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/we3io/ai-assistant-rules/guardrailsgit clone --depth 1 https://github.com/WE3io/ai-assistant-rulesWrote 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/we3io/ai-assistant-rules/guardrails)<a href="https://agentmods.dev/rules/we3io/ai-assistant-rules/guardrails"><img src="https://agentmods.dev/badge/rules/we3io/ai-assistant-rules/guardrails.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 | $0.01085 | $0.01085 |
| Opus 5 | $0.00543 | $0.00543 |
| Sonnet 5 | $0.00217 | $0.00217 |
| Haiku 4.5 | $0.00109 | $0.00109 |
Grade A, and why
guardrails 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 3d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 3d ago First seen · 202 lines · 1,085 tokens per session scan A 19802944d115
guardrails is a cursor rule published in the GitHub repository WE3io/ai-assistant-rules (2 stars, last pushed 6mo ago), with no licence file. It adds 1,085 tokens to every session, about $0.0054 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
cursorrules
Decide single- or multi-workstream (look at file naming under brain/).
cursorrules
You are an expert backend API developer. Follow these rules strictly for REST APIs, GraphQL servers, and microservices.
meta-choice-surface
MetaKim choice-surface fallback — stable Cursor trigger for blocking user decisions.
django-middleware
关于使用 Django 中间件处理认证、日志和缓存等横切关注点的指南。.
minimax-m3-status-verification
MiniMax M3 status and verification contract: exact claim labels, proof matching, multimodal-grounded visual claims, and evidence-first closeouts.
minimax-mcp-tools
MCP and web-tool guidance: current-doc retrieval, direct-tool preference, MCP Apps structured content, and version-aware external lookups.