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.
npx agentmods add commands/berrzebb/quorum/cl-orchgit clone --depth 1 https://github.com/berrzebb/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/commands/berrzebb/quorum/cl-orch)<a href="https://agentmods.dev/commands/berrzebb/quorum/cl-orch"><img src="https://agentmods.dev/badge/commands/berrzebb/quorum/cl-orch.svg" alt="Measured on agentmods" 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.00019 | $0.00069 |
| Opus 5 | $0.00010 | $0.00034 |
| Sonnet 5 | $0.00004 | $0.00014 |
| Haiku 4.5 | $0.00002 | $0.00007 |
Grade A, and why
cl-orch 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 6d 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
Invoke the orchestrator skill: /quorum:orchestrator {{ task_id }}
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.
- 6d ago First seen · 11 lines · 19 tokens per session scan A 87a71016b70b
cl-orch is a command published in the GitHub repository berrzebb/quorum (10 stars, last pushed 4mo ago), licensed MIT. It adds 19 tokens to every session and 69 once invoked, about $0.0001 per session on Opus 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 commands, from other repositories
krait-poc
Write and run a valid Foundry proof-of-concept that proves (or disproves) a Solidity exploit by asserting the actual harm on a forked chain or against local source.
benchmark-compare
Run the harness bench tier on the working tree and on a ref (default origin/main) in the deterministic configuration, and report per Floor id — Floor, ref value, current value, delta, pass/fail — per row, never per total. Records to harness/results/latest.json only on a clean main; otherwise says where the scratch…
compliance
이전 보안 진단 보고서의 Finding들이 패치되었는지 확인하고, 변경된 코드에서 신규 취약점을 탐색합니다.
verify
Adversarial Verification — 보안 진단 보고서 독립 검증 (Autonomous First).
deploy
Deploy the app.
krait-review
Re-examine findings killed by the Critic's automatic gates. Catches over-filtering without compromising the main report's zero-FP standard.