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 rules/tholem-ai/tholem-cursor-kit/010-governancegit clone --depth 1 https://github.com/Tholem-AI/Tholem-Cursor-KitWrote 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/tholem-ai/tholem-cursor-kit/010-governance)<a href="https://agentmods.dev/rules/tholem-ai/tholem-cursor-kit/010-governance"><img src="https://agentmods.dev/badge/rules/tholem-ai/tholem-cursor-kit/010-governance.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.00248 | $0.00248 |
| Opus 5 | $0.00124 | $0.00124 |
| Sonnet 5 | $0.00050 | $0.00050 |
| Haiku 4.5 | $0.00025 | $0.00025 |
Grade A, and why
010-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 5d 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
010-governance
Purpose
Define always-on governance shared by all runtime rules.
Mandatory policy
- Require explicit user approval before high-impact actions, including: architecture changes, structural moves/renames, stack changes, or git writes.
- Escalate contradictions across runtime rules, roadmap, manifest, and migration runbook before continuing.
- Keep runtime artifacts operational-only. Move tutorials, long examples, and narrative rationale to docs.
- Keep
ROADMAP.mdand relevant docs aligned with actual implementation state. - Do not reactivate deprecated workflow artifacts (for example legacy task or memory archive files) as active execution targets unless explicitly approved by the user.
Rule boundaries
- Governance defines cross-cutting authority.
- Execution lifecycle policy lives in
.cursor/rules/020-execution.mdc. - Safety constraints live in
.cursor/rules/030-safety.mdc. - Validation gates live in
.cursor/rules/040-quality.mdc. - Stack constraints live in
.cursor/rules/050-project-constraints.mdc.
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.
- 5d ago First seen · 31 lines · 248 tokens per session scan A 84a242c22557
010-governance is a cursor rule published in the GitHub repository Tholem-AI/Tholem-Cursor-Kit (4 stars, last pushed 3mo ago), licensed MIT. It adds 248 tokens to every session, about $0.0012 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.