Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add berrzebb/quorum/plugin install quorumWrote 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/agents/berrzebb/quorum/scout)<a href="https://agentmods.dev/agents/berrzebb/quorum/scout"><img src="https://agentmods.dev/badge/agents/berrzebb/quorum/scout/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/berrzebb/quorum/scout"><img src="https://agentmods.dev/badge/agents/berrzebb/quorum/scout.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00063 | $0.00606 |
| Opus 5.5 | $0.00025 | $0.00242 |
| Sonnet 5.5 | $0.00013 | $0.00121 |
| Haiku 4.5 | $0.00006 | $0.00061 |
Grade A, and why
scout 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 1mo 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
Scout Protocol (Claude Code)
Read the full protocol: ${CLAUDE_PLUGIN_ROOT}/../../../agents/knowledge/protocols/scout.md
This file contains only Claude Code-specific bindings. All phases, output rules, and anti-patterns are in the shared protocol.
Path Variables
- RTM format reference:
${CLAUDE_PLUGIN_ROOT}/../../core/templates/references/${locale}/traceability-matrix.md
Claude Code Tool Mapping
| Operation | Tool |
|---|---|
| Read file | Read |
| Find files | Glob |
| Search content | Grep |
| Run shell | Bash |
Tool Invocation
All deterministic tools are available via CLI:
node "${CLAUDE_PLUGIN_ROOT}/../../core/tools/tool-runner.mjs" <tool_name> --param value
Available tools: code_map, dependency_graph, audit_scan, coverage_map.
Add --json for structured output when you need programmatic access to results.
| Task | CLI Command |
|---|---|
| File/symbol existence | node tool-runner.mjs code_map --path <dir> |
| Import chains | node tool-runner.mjs dependency_graph --path <dir> |
| Pattern detection | node tool-runner.mjs audit_scan --pattern all |
| Coverage data | node tool-runner.mjs coverage_map --path <filter> |
Where tool-runner.mjs is at ${CLAUDE_PLUGIN_ROOT}/../../core/tools/tool-runner.mjs.
Language-Aware Scanning
Pattern detection (audit_scan) automatically loads all language specs from languages/registry.mjs. Each language's qualityRules patterns are scanned for their matching file extensions — no manual filtering needed.
Output
Write via single Write tool (not sequential Edits) — same atomic pattern as evidence submission.
Output files saved at {planning_dir}/:
rtm-{domain}.md— per-track RTM (3 matrices)gap-report-{domain}.md— actionable gap reportcross-track-connections.md— cross-track import chain audit
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.
- 1mo ago First seen · 68 lines · 63 tokens per session scan A e463d0ec1ec0
scout is an agent published in the GitHub repository berrzebb/quorum (10 stars, last pushed 6mo ago), licensed MIT. It adds 63 tokens to every session and 606 once invoked, about $0.0003 per session on Opus 5.5. 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 agents, from other repositories
Smart Exclude
Picks folders a SAST run doesn't need to scan (test directories, fixtures, docs, generated code, vendored deps) so the scan skips them.
reviewer
A code-review agent that examines changes for correctness, readability, testing, security, consistency, and traceability.
Validate
Dedicated agent for running validation commands (build, typecheck, lint, test). Reports pass/fail with structured failure details - never fixes.
adversarial-planner
Independent adversary for an implementation PLAN, before any code is written. Attacks the written plan's scope, non-goals, and decisions against the committed constraints it must honor, and surfaces only grounded objections for the human to decide. Never rewrites the plan and never sees the author's reasoning …
code-reviewer
You are a specialized code review subagent for Visor. Your role is to perform deep, comprehensive code reviews with a focus on.
pr-creator
Use for creating and editing pull requests via gh pr create, gh pr edit, gh pr view, gh pr diff, and gh pr list. Does NOT merge or mark ready (use pr-merger for that). A Bash command denied by the harness permission system is surfaced to the operator, never reshaped to evade the denial.