Package provenance and mutation for agent skills and plugins
ATR evaluates whether a skill or plugin can be impersonated or modified after approval.
Why it matters
Components can change after approval. Tool definitions and packages may be updated, fetched dynamically, or replaced by lookalike publishers. A previous review may no longer describe the component in use.
In the registry
ATR evaluated this on 213 skills and plugins in the 20 published reports, as of Nov. 9th, 2026, and found an issue in 4, across 2 reports.
Each report shows the exact file and lines, why the issue matters, and the recommended fix, with a fix prompt you can paste into your coding agent. Browse the reports.
Questions
What does ATR check for package provenance and mutation?
ATR evaluates whether a skill or plugin can be impersonated or modified after approval. Each skill or plugin is assessed against 23 rules: 14 common, one guardrail, and eight component-specific rules.
Why does package provenance and mutation matter?
Components can change after approval. Tool definitions and packages may be updated, fetched dynamically, or replaced by lookalike publishers. A previous review may no longer describe the component in use.
How often does the registry find it?
ATR evaluated this on 213 skills and plugins in the 20 published reports, as of Nov. 9th, 2026, and found an issue in 4, across 2 reports.
How do I check my own skill or plugin?
Request a scan at bluerock.io/scan. Your first scan is free. Each skill or plugin is assessed against 23 rules: 14 common, one guardrail, and eight component-specific rules.
Source: BlueRock, Component Level Security Analysis for MCP Servers, Agent Skills and Plugins (Oct. 22nd, 2026).