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 agents/berrzebb/quorum/doc-syncgit clone --depth 1 https://github.com/berrzebb/quorumWhat 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 | $0.00039 | $0.00466 |
| Opus 5 | $0.00019 | $0.00233 |
| Sonnet 5 | $0.00008 | $0.00093 |
| Haiku 4.5 | $0.00004 | $0.00047 |
Grade A, and why
doc-sync 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 2d 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
Doc-Sync Agent (Claude Code)
Read and follow:
- Protocol:
${CLAUDE_PLUGIN_ROOT}/../../../agents/knowledge/doc-sync-protocol.md
Claude Code Tool Invocation
# Fact extraction
node -e "const h=JSON.parse(require('fs').readFileSync('platform/adapters/claude-code/hooks/hooks.json','utf8'));console.log(h.hooks.length)"
node -e "const h=JSON.parse(require('fs').readFileSync('platform/adapters/gemini/hooks/hooks.json','utf8'));console.log(h.hooks.length)"
node -e "const h=JSON.parse(require('fs').readFileSync('platform/adapters/codex/hooks/hooks.json','utf8'));console.log(h.hooks.length)"
node -e "console.log(JSON.parse(require('fs').readFileSync('package.json','utf8')).version)"
Execution Flow
- Extract — run all fact extraction commands from protocol
- Scan — grep each doc file for numeric assertions
- Compare — match extracted facts against doc assertions
- Fix — Edit mismatched lines, add missing sections
- Report — output Doc-Sync Report in protocol format
Anti-Patterns
- Do NOT change prose or explanations — only facts and structure
- Do NOT add sections that don't correspond to actual code features
- Do NOT remove sections even if the feature seems deprecated — flag for manual review
- Do NOT run destructive git commands
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.
- 2d ago First seen · 43 lines · 39 tokens per session scan A 6a2a91896971
doc-sync is an agent published in the GitHub repository berrzebb/quorum (10 stars, last pushed 4mo ago), licensed MIT. It adds 39 tokens to every session and 466 once invoked, about $0.0002 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 agents, from other repositories
auditor
GxP audit and investigation specialist for audit planning, execution, finding classification, CAPA root cause analysis, inspection readiness, data integrity monitoring, and vendor qualification.
learning-curator
Captures a learning candidate from a surprise, incident, or review finding into .charter/learning/inbox/.
Code Reviewer
Quality assurance reviewer for pull request review, standards enforcement, and code quality assessment.
bead-epic-auditor
Use this agent when auditing bead epics for closure drift — finding open epics whose entire child set is already closed (so their GitHub/Plane cluster issue never got the close fan-out), or otherwise reasoning about epic/subtree completion across a bd Dolt database.
auditor
Dual-flywheel auditor — captures learning candidates and prunes dead rules from the charter.
DevOps Engineer
Infrastructure and CI/CD specialist for Docker, Kubernetes, GitHub Actions, deployment, and monitoring.