Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
/plugin marketplace add MadAppGang/magusnpx agentmods add plugins/madappgang/magus/code-analysisgit clone --depth 1 https://github.com/MadAppGang/magusGrade A, and why
code-analysis scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"name": "code-analysis",
"version": "7.1.0",
"description": "Read-only codebase investigation and code search behind one stable tool surface. Finds code by meaning or structure, traces callers, callees and blast radius, and dispatches a detective agent for deep dives. The search engine is named in project settings and is swappable.",
"author": {
"name": "Jack Rudenko",
"email": "[email protected]",
"company": "MadAppGang"
},
"license": "MIT",
"keywords": [
"code-analysis",
"codebase",
"investigation",
"architecture",
"patterns",
"debugging",
"code-navigation",
"semantic-search",
"mcp",
"ast",
"structural-analysis"
],
"category": "development",
"dependencies": [
{
"name": "claudish",
"version": "^2.0"
}
],
"skills": [
"./skills/code-search",
"./skills/deep-analysis",
"./skills/investigate"
],
"mcpServers": "./.mcp.json",
"conventions": {
"gitignore": {
"project": [
".mnemex/"
],
"global": [
".claudemem/",
".claude/.coaching/"
]
},
"claudemd": {
"section": "code-analysis",
"template": "./templates/claude-md-conventions.md",
"version": "2.0.0"
}
}
}
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 54 lines scan A 20bb1cf5ef43
code-analysis is a plugin published in the GitHub repository MadAppGang/magus (9 stars, last pushed 3d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other plugins, from other repositories
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.
nextjs
Official Claude Code plugin marketplace for Next.js, serving the skills that ship in the vercel/next.js repository.
claude-plugins-official
Directory of popular Claude Code extensions including development tools, productivity plugins, and MCP integrations.
knowledge-work-plugins
Plugin marketplace listing 97 plugins: noibu, productivity, enterprise-search, cowork-plugin-management, sales.
ecc
Plugin marketplace listing 1 plugin: ecc.
ecc
Harness-native ECC plugin for engineering teams - 68 agents, 286 skills, 94 legacy command shims, reusable hooks, rules, MCP conventions, and operator workflows for Claude Code plus adjacent agent harnesses.