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/archgate/cliWrote 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/rules/archgate/cli/archgate-governance)<a href="https://agentmods.dev/rules/archgate/cli/archgate-governance"><img src="https://agentmods.dev/badge/rules/archgate/cli/archgate-governance/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/rules/archgate/cli/archgate-governance"><img src="https://agentmods.dev/badge/rules/archgate/cli/archgate-governance.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.00195 | $0.00195 |
| Opus 5.5 | $0.00078 | $0.00078 |
| Sonnet 5.5 | $0.00039 | $0.00039 |
| Haiku 4.5 | $0.00019 | $0.00019 |
Grade A, and why
archgate-governance 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
Archgate Governance
This project uses Archgate to enforce Architecture Decision Records (ADRs).
Before writing code
- Use the
review_contextMCP tool to get applicable ADR briefings for changed files - Review the Decision and Do's/Don'ts sections of each applicable ADR
After writing code
- Run the
checkMCP tool to validate compliance with all ADR rules - Fix any violations before considering work complete
ADR commands
list_adrs— List all active ADRs with metadatacheck— Run automated compliance checks (usestaged: truefor pre-commit)review_context— Get changed files grouped by domain with ADR briefings
Key principle
Architectural decisions are enforced, not suggested. If check reports violations, they must be fixed.
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 · 30 lines · 195 tokens per session scan A d7304eddf493
archgate-governance is a cursor rule published in the GitHub repository archgate/cli (72 stars, last pushed 2d ago), licensed Apache-2.0. It adds 195 tokens to every session, about $0.0008 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-30.
Other cursor rules, from other repositories
planning-adrs
ADR format for docs/adr — Nygard sections, numbering, status.
planning-queue
Working queue in docs/queue.md — keep aligned with backlog and stories.
planning-stories
Planning story conventions for docs/stories — follow doccraft-story.
prompt-to-asset
Asset generation — route, rewrite, generate, validate. Never send transparency requests to Imagen/Gemini.
swamr-orchestrator
Swamr Orchestrator — autonomous agent swarm that builds entire projects. Invoke with @swamr-orchestrator followed by what you want built. Decomposes into tasks, selects specialist agents, runs dev↔QA loops, and delivers production-ready code.
swamr-state-manager
Swamr State Manager — tracks task progress, manages the execution pipeline, handles retries and escalation. Maintains swamr/state.json as the single source of truth for swarm progress.