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/movahedan/monobunWrote 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/movahedan/monobun/repo-invariants)<a href="https://agentmods.dev/rules/movahedan/monobun/repo-invariants"><img src="https://agentmods.dev/badge/rules/movahedan/monobun/repo-invariants/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/movahedan/monobun/repo-invariants"><img src="https://agentmods.dev/badge/rules/movahedan/monobun/repo-invariants.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.00379 | $0.00379 |
| Opus 5 | $0.00189 | $0.00189 |
| Sonnet 5 | $0.00076 | $0.00076 |
| Haiku 4.5 | $0.00038 | $0.00038 |
Grade A, and why
repo-invariants 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 10d 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
Repo invariants
Context map
| Need | Read |
|---|---|
| Repo layout, packages | AGENTS.md |
| Compose / layout / troubleshooting | AGENTS.md |
| Commands (tables) / troubleshooting | docs/CHEATSHEET.md |
| Area you edit | Nested AGENTS.md under that apps/ or packages/ path |
| Security | security.mdc |
| TypeScript / React deltas | typescript.mdc when editing .ts / .tsx |
| Multi-phase work | initiative-workflow |
Quality gate
Before claiming work is done or opening a PR: bun run overall (unless the approved plan lists a narrower gate).
Secrets and config
- Never commit
.env, credentials, or API keys. - Read required env vars at use site; throw if missing (do not assume defaults for secrets).
Initiative work
Phased features: planning-workflow → builder-workflow (code only) → documentation-sync (plan doc list) → git-pr-workflow. See initiative-workflow.
Subagents
Spawn policy lives in builder-workflow and orchestration.md — not in rules.
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.
- 10d ago First seen · 36 lines · 379 tokens per session scan A fa4452c58ca3
repo-invariants is a cursor rule published in the GitHub repository movahedan/monobun (18 stars, last pushed today), licensed MIT. It adds 379 tokens to every session, about $0.0019 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-30.
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.