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 VoltAgent/awesome-claude-code-subagentsnpx agentmods add plugins/voltagent/awesome-claude-code-subagents/10-research-analysisgit clone --depth 1 https://github.com/VoltAgent/awesome-claude-code-subagentsGrade A, and why
voltagent-research 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 3d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- voltagent-research — 100% identical, 0 lines differ
What it actually says
{
"name": "voltagent-research",
"version": "1.0.4",
"description": "Research, search, and analysis specialists - market research, competitive analysis, trend forecasting, and idea validation",
"author": {
"name": "VoltAgent Community",
"url": "https://github.com/VoltAgent"
},
"repository": "https://github.com/VoltAgent/awesome-claude-code-subagents",
"license": "MIT",
"agents": [
"./ab-test-analysis.md",
"./cohort-analysis.md",
"./competitive-analyst.md",
"./data-researcher.md",
"./first-principles-thinking.md",
"./market-researcher.md",
"./project-idea-validator.md",
"./research-analyst.md",
"./scientific-literature-researcher.md",
"./search-specialist.md",
"./trend-analyst.md"
]
}
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.
- 3d ago First seen · 25 lines scan A 5325f2725d7b
voltagent-research is a plugin published in the GitHub repository VoltAgent/awesome-claude-code-subagents (24,790 stars, last pushed yesterday), 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-30.
Other plugins, from other repositories
cto-team-marketplace
Plugin marketplace listing 1 plugin: cto-team.
claude-cto-team
Strategic CTO advisory team with specialized agents for architecture design, plan validation, and technology decisions.
section-508
Expert Section 508 compliance advisor for US federal ICT accessibility — VPAT/ACR completion, WCAG 2.0 AA audits, remediation planning, PDF accessibility, procurement language, keyboard and screen reader testing, undue burden assessments, and agency compliance workflows.
ask-llm
AI-to-AI collaboration — review code and debate plans across Codex, Grok, Antigravity, Ollama, and Gemini.
debugger
Debugging specialist for errors, test failures, and unexpected behavior. Use proactively when encountering any issues.
compact-manager
Warns the main session as its own context fills, captures a wake packet before compaction, and reorients the session after it — so an autonomous orchestrator survives past one context window.