qa-orchestra

Install

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.

Security

Grade A, and why

qa-orchestra 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.

.claude-plugin/plugin.json · 31 lines

What it actually says

{
  "name": "qa-orchestra",
  "version": "1.1.0",
  "description": "10 coordinated QA agents for Claude Code: chains diff analysis, AC compliance, test scenarios, browser validation, bug reports, and automation code generation.",
  "author": {
    "name": "Anass R.",
    "url": "https://github.com/Anasss"
  },
  "homepage": "https://qa-orchestra.com",
  "repository": "https://github.com/Anasss/qa-orchestra",
  "license": "MIT",
  "keywords": [
    "qa",
    "testing",
    "agents",
    "orchestrator",
    "browser-validation",
    "functional-review",
    "test-scenarios",
    "bug-reports",
    "acceptance-criteria",
    "diff-analysis",
    "playwright",
    "claude-code-plugin"
  ],
  "screenshots": [
    "docs/images/qa-orchestra-detective.webp"
  ],
  "agents": "./.claude/agents/"
}

Contents

What it installs

The manifest is a name and a version. 10 agents travel with it, and installing the plugin installs all of them — 264 tokens a session between them. Each is measured on its own page, and each can be installed alone.

Files

What ships with it

1 file beside plugin.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.

Changes

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.

Related

Other plugins, from other repositories