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.
git 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-guide)<a href="https://agentmods.dev/commands/berrzebb/quorum/cl-guide"><img src="https://agentmods.dev/badge/commands/berrzebb/quorum/cl-guide/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/commands/berrzebb/quorum/cl-guide"><img src="https://agentmods.dev/badge/commands/berrzebb/quorum/cl-guide.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.00014 | $0.00033 |
| Opus 5.5 | $0.00006 | $0.00013 |
| Sonnet 5.5 | $0.00003 | $0.00007 |
| Haiku 4.5 | $0.00001 | $0.00003 |
Grade A, and why
cl-guide 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
Invoke the guide skill: /quorum:guide
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 · 7 lines · 14 tokens per session scan A b6a3574c69a0
cl-guide is a command published in the GitHub repository berrzebb/quorum (10 stars, last pushed 6mo ago), licensed MIT. It adds 14 tokens to every session and 33 once invoked, about $0.0001 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 commands, from other repositories
test
Write tests using MCP-powered discovery.
implement
Implement features using plan and MCP verification.
plan
Create implementation plan using MCP-powered discovery.
review
Review changes using MCP validation.
boot
Command "boot" from ready-to-release/eac, covering boot, instructions, example initialization report and notes.
CHANGELOG
All notable changes to eac-mcp-server will be documented in this file. The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.