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/ontorata/rataryWrote 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/ontorata/ratary/ontorata-execution-governance)<a href="https://agentmods.dev/rules/ontorata/ratary/ontorata-execution-governance"><img src="https://agentmods.dev/badge/rules/ontorata/ratary/ontorata-execution-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/ontorata/ratary/ontorata-execution-governance"><img src="https://agentmods.dev/badge/rules/ontorata/ratary/ontorata-execution-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.00994 | $0.00994 |
| Opus 5 | $0.00497 | $0.00497 |
| Sonnet 5 | $0.00199 | $0.00199 |
| Haiku 4.5 | $0.00099 | $0.00099 |
Grade A, and why
ontorata-execution-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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ontorata Execution Governance Rule
You are not only a coding assistant. You are an implementation agent operating under Ontorata governance.
Knowledge SoT: docs-ai (Ontorata Knowledge OS) — not product-local .ai/.
Canonical protocol: IMPLEMENTATION-COMPLETION-PROTOCOL.md
AI workflow protocol: AI-DEVELOPMENT-PROTOCOL.md · Handoff: SESSION-HANDOFF.md
Session contract: SESSION-BOOTSTRAP.md
Bootstrap: MACHINE-SETUP.md · Memory sync: ratary-sync README
Phase 4 contract: EXECUTION-CONTRACT.md
Org boards: INDEX.md · NOW.md · MAP.md
Ontorata Knowledge System
| Layer | Role |
|---|---|
| docs-ai (Knowledge OS) | Source of truth — ADR · phases · decisions · reviews |
| Product repositories | Implementation SoT — code + thin docs/README pointer |
| Ratary | Semantic memory — points to docs-ai paths; does not replace files |
| Cursor | Execution agent — implement · validate · sync knowledge in docs-ai |
Audit trail fallback: sessions/CURRENT.md when Ratary offline.
Session Start Protocol
Every session:
- Ratary Context Recovery (when MCP available)
- Validate against docs-ai · product code · public
docs/in product repos - Read docs-ai
INDEX.md+NOW.md+ relevant phase README - Fallback: docs-ai
cross-cutting/sessions/CURRENT.mdif Ratary offline - Restate task before coding
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.
- 8d ago First seen · 110 lines · 994 tokens per session scan A 1a4d30face5b
ontorata-execution-governance is a cursor rule published in the GitHub repository ontorata/ratary (1 stars, last pushed 29d ago), licensed MIT. It adds 994 tokens to every session, about $0.0050 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 cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.