# An add-on for your AI tool can change after you install it

Security · For Cursor, Claude Code, Gemini CLI and Devin Desktop · Published 2026-11-14 · Last checked against the source 2026-11-16
Web page: https://vibe.ikangai.com/notices/agent-add-ons.html

> Add-ons give your AI coding tool extra instructions. Some load part of those instructions from the internet every time they run, so whoever controls that address can change what your tool does.

## Does this apply to you?

It applies if any of these is true:

- You installed add-ons (skills, rules files or MCP servers) from a marketplace, from GitHub or from a social media post.
- You let your AI tool choose which ready-made code libraries to install.

## What is the problem?

Skills, rules files and MCP servers are add-ons that give your AI coding tool extra instructions and abilities. Most people install them the way they install an app: once, from a link someone shared.

But an add-on can load part of its instructions from a web address every time it runs. Whoever controls that address can change what the add-on tells your AI tool tomorrow, and the file on your computer will look exactly the same.

## What could happen?

A team from Snyk scanned a shared add-on for researching competitors. It told the AI tool to print a login token, which can leak it into the tool’s records, and it fetched its rules from a file hosted on the internet.

In the same talk they compared two ready-made code libraries that an AI tool had picked for a small task. Neither had a known security flaw, but only one was still being looked after, so a future flaw in the other is less likely to get fixed.

## What should you do?

1. Ask your AI tool to check what is installed. Paste this message.

   Message to paste:

   ```text
   Go through every skill, rules file and MCP server set up for this project and for my user account. Do not run any of them. For each one, tell me:
   1. Does it fetch instructions or content from a web address when it runs?
   2. Does it ask you to print, log or send any key, token or login header?
   Give me the file and line for each finding.
   ```

2. Remove any add-on that fetches instructions from the web or prints keys, unless you know and trust who maintains it.
3. Make your AI tool check code libraries before it adds them. Paste this at the start of a session, or add it to your project’s standing instructions.

   Message to paste:

   ```text
   From now on, before you add any package, show me when it was last updated and whether it is still maintained, and prefer the maintained option.
   ```

4. Before you install the next add-on, check who published it and when it was last updated.
5. If someone else looks after your app, send them this notice.

## Where this comes from

Manoj Nair, Ezra Tanzer and Randall Degges, Snyk. [Through the AI Fog: The architectural decision the next 24 months of agentic security depends on](https://ai.engineer/talks/1EZdpEhwmNc-through-ai-fog-architectural-decision-next-24). AI Engineer World’s Fair 2026.

- [15:30 Two code libraries with no known flaws, compared](https://www.youtube.com/watch?v=1EZdpEhwmNc&t=930s)
- [18:55 Scanning a shared add-on](https://www.youtube.com/watch?v=1EZdpEhwmNc&t=1135s)

Vendor talk: Both demos use the speakers’ own commercial tools.

How we adapted it: The speakers recommend making the library check automatic so that it runs every time; step 3 is the manual version. The check in step 1 is ours.
