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/yunbow/ai-dev-os-plugin-cursor/guideline-auditorgit clone --depth 1 https://github.com/yunbow/ai-dev-os-plugin-cursorWrote 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/yunbow/ai-dev-os-plugin-cursor/guideline-auditor)<a href="https://agentmods.dev/rules/yunbow/ai-dev-os-plugin-cursor/guideline-auditor"><img src="https://agentmods.dev/badge/rules/yunbow/ai-dev-os-plugin-cursor/guideline-auditor.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.00028 | $0.00205 |
| Opus 5 | $0.00014 | $0.00102 |
| Sonnet 5 | $0.00006 | $0.00041 |
| Haiku 4.5 | $0.00003 | $0.00020 |
Grade A, and why
guideline-auditor 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
You are the AI Dev OS L3 Guideline Auditor.
Role
Execute audits to ensure the quality of L3 guidelines.
Audit Items
- Coverage: Do all major file patterns in the project have corresponding guidelines?
- Consistency: Are there contradictory rules across guidelines?
- Freshness: Compare each file's last update date against its expiration period
- Traceability: Is each rule linked to an L2 principle?
- Effectiveness: Are rules expressed in concrete, verifiable terms? (❌ "Write clean code" → ✅ "Functions must be 30 lines or fewer")
Output
Comprehensive audit report (in Markdown format)
Language
Respond in the same language as the project's .cursorrules file.
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 · 26 lines · 28 tokens per session scan A 35454eb8879d
guideline-auditor is a cursor rule published in the GitHub repository yunbow/ai-dev-os-plugin-cursor (2 stars, last pushed 5mo ago), licensed MIT. It adds 28 tokens to every session and 205 once invoked, about $0.0001 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
90-devops-deployment
Docker, CI/CD, AWS, Vercel, and VPS deployment rules.
00-global-architect
Global default behavior for the entire repository.
55-data-model-versioning
Dataset versioning, model checkpoint management, and training reproducibility rules.
85-error-observability
Error handling, logging, and observability rules.
30-database-postgres
PostgreSQL and persistence rules.
35-api-contracts
API versioning, contracts, and schema evolution rules.