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 Anasss/qa-orchestranpx agentmods add plugins/anasss/qa-orchestra/marketplacegit clone --depth 1 https://github.com/Anasss/qa-orchestraWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/plugins/anasss/qa-orchestra/marketplace)<a href="https://agentmods.dev/plugins/anasss/qa-orchestra/marketplace"><img src="https://agentmods.dev/badge/plugins/anasss/qa-orchestra/marketplace.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
qa-orchestra marketplace 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 4d 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": "qa-orchestra",
"metadata": {
"description": "Multi-agent QA toolkit for Claude Code — 10 specialized agents covering the full QA lifecycle from diff analysis to bug reports."
},
"owner": {
"name": "Anass R.",
"url": "https://github.com/Anasss"
},
"plugins": [
{
"name": "qa-orchestra",
"description": "10 coordinated QA agents: functional reviewer, test scenario designer, automation writer, bug reporter, browser validator, and more. Full QA lifecycle from diff analysis to bug reports.",
"version": "1.1.0",
"source": {
"source": "github",
"repo": "Anasss/qa-orchestra",
"path": "."
}
}
]
}
The plugins it lists here
This marketplace lists 1 plugin kept in the same repository. Each has its own page, its own measurements and its own install command.
What ships with it
1 file beside marketplace.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 23 lines scan A eb6df30f4c63
qa-orchestra marketplace is a plugin published in the GitHub repository Anasss/qa-orchestra (12 stars, last pushed 4mo 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-30.
Other plugins, from other repositories
swarm-skill
Multi-agent codebase audit skill for Claude Code — spawns parallel subagents (security, performance, tests, architecture, dead-code) and synthesizes their findings into a prioritized action plan.
self-review
Review every code change before the turn ends: fresh-context reviewer agents, a verified finding standard, honest convergence, and a measured token budget — enforced by a Stop hook, graph-aware when you have a code graph, zero-cost when you don't.
dev-pipeline
A 5-phase development pipeline (requirement engineering, system architecture, task generation, verified implementation, code review) with an optional QA gate (plan-qa + execute-qa) for changes that have a running surface worth driving — independent of /review, run sequentially or in parallel at the developer's…
claudeboss
Delegate tasks to free opencode agents and supervise them from Claude Code — Team mode (pair review) or Boss mode (manage, approve, deploy).
accessibility
WCAG 2.2 AA accessibility auditing and design guidance. Review mode audits existing code; design mode guides building accessible components.
adr
Creates and maintains Architecture Decision Records (ADRs) in MADR format. Supports create, list, update, supersede, and search.