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/Jott2121/agent-gateWrote 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/jott2121/agent-gate/00-core-principles)<a href="https://agentmods.dev/rules/jott2121/agent-gate/00-core-principles"><img src="https://agentmods.dev/badge/rules/jott2121/agent-gate/00-core-principles/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/jott2121/agent-gate/00-core-principles"><img src="https://agentmods.dev/badge/rules/jott2121/agent-gate/00-core-principles.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.00250 | $0.00250 |
| Opus 5.5 | $0.00100 | $0.00100 |
| Sonnet 5.5 | $0.00050 | $0.00050 |
| Haiku 4.5 | $0.00025 | $0.00025 |
Grade A, and why
00-core-principles 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 4d 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
Core principles (always on)
- Personal work only. Never add anything from an employer's systems, workforce data, internal URLs, or confidential or export-restricted material: no employer names, acronyms, documents, or realistic HR records. Synthetic data from a seeded, committed generator only. If unsure where content came from, stop and ask.
- Every claim needs a receipt: a committed command that reproduces it and the artifact it produces. No adjectives without numbers.
- Report nulls/regressions as prominently as wins. State n, seeds, model+version, date, cost.
- Decision paths fail closed (deny on error/timeout/missing input). Never weaken a guard, threshold, or coverage floor to get green.
- Done = lint + tests pass and the output is pasted in the PR. New behavior ships with a test that fails without it.
- No irreversible actions: no force-push, history rewrite, release tagging, package publishing, or posting. Open a PR.
- See AGENTS.md for commands. Run them; don't guess.
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.
- 4d ago First seen · 14 lines · 250 tokens per session scan A 4002aec93214
00-core-principles is a cursor rule published in the GitHub repository Jott2121/agent-gate (3 stars, last pushed yesterday), licensed MIT. It adds 250 tokens to every session, about $0.0010 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-10-12.
Other cursor rules, from other repositories
git-conventions
See CONTRIBUTING.md → "PR & commit conventions" for PR title format, commit messages, and branch naming.
python-github-setup-cursorrules-prompt-file
Cursor rules for Python development with GitHub setup integration.
roslyn-mcp-version-bump
Auto-bump Version after successful MCP self-build and reload.
git_workflow
Git Workflow and Configuration for AGB SDK.
conventional-commits
Enforce Conventional Commits format for all commit messages.
new-project-standard
Local adoption files are authoritative. Remote links are navigation only and must not be fetched or executed at runtime.