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/logi-cmd/agent-guardrails/cursorgit clone --depth 1 https://github.com/logi-cmd/agent-guardrailsWhat 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 | $0.00106 | $0.00106 |
| Opus 5 | $0.00053 | $0.00053 |
| Sonnet 5 | $0.00021 | $0.00021 |
| Haiku 4.5 | $0.00011 | $0.00011 |
Grade A, and why
cursor 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 2d 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
agent-guardrails: ALWAYS run before finishing
Before telling the user a task is done, you MUST:
- Run:
npx agent-guardrails check --base-ref HEAD~1 - If issues found → fix them first, do NOT say "done"
- If clean → include the check result in your summary
- If command not found → tell user to run
npx agent-guardrails setup
This is not optional. Skipping this check means the task is incomplete.
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.
- 2d ago First seen · 10 lines · 106 tokens per session scan A d2fd42d9184f
cursor is a cursor rule published in the GitHub repository logi-cmd/agent-guardrails (30 stars, last pushed 16d ago), licensed MIT. It adds 106 tokens to every session, about $0.0005 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
p8-enforcement
P8 Enforcement Rules — Injected into every Agent conversation.
cursor
You are working on the checkout service. Preserve transaction integrity and auditability.
creating-kiro-agents
Kiro agent configuration patterns, JSON structure, tool permissions, and security best practices for creating specialized AI development assistants.
archcore-files
Enforce MCP-only operations when working with .archcore/ files.
test-plan
Plan Katalon True Platform/TestOps testing for a release, sprint, or feature. Use when you need to translate quality goals into scope, prioritize testing by requirement coverage and risk, decide what to test first, or build the executable plan structure (folders, suites, and sprint/release association) that stands in…
dev_workflow
Guide for using Taskmaster to manage task-driven development workflows.