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/ai-dev-os-checkgit 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/ai-dev-os-check)<a href="https://agentmods.dev/rules/yunbow/ai-dev-os-plugin-cursor/ai-dev-os-check"><img src="https://agentmods.dev/badge/rules/yunbow/ai-dev-os-plugin-cursor/ai-dev-os-check.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.00059 | $0.00895 |
| Opus 5 | $0.00030 | $0.00447 |
| Sonnet 5 | $0.00012 | $0.00179 |
| Haiku 4.5 | $0.00006 | $0.00089 |
Grade A, and why
ai-dev-os-check 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.
How it starts
The opening of the file, as written. The whole thing — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Dev OS Guideline Check & Fix
Design Principle: Report-only checks have near-zero impact on code quality. Check + Fix in a single session achieves +9.9 improvement (benchmark Test 011).
Execution Flow
1. Determine Scope & Mode
Ask the user or infer the check scope and mode:
Scope:
- Default: Check unstaged changes (
git diff --name-only) - Staged: Check staged changes (
git diff --cached --name-only) - Branch comparison (e.g.,
main): Check all changes vs. the specified branch (git diff [branch]...HEAD --name-only) — ideal for PR review
Mode:
- Default: Check & Fix — find violations and fix them automatically
--dry-run: Report only — list violations without modifying code
2. Parse .cursorrules
Extract the list of guideline file paths from .cursorrules (or CLAUDE.md / AGENTS.md if present).
3. Get Changed Files
Retrieve changed files based on the determined scope. If no files are changed, report "No changes to check" and exit.
4. Select Checklist
Auto-detect the tech stack from the project and load the appropriate checklist template:
.cursor/checklist-templates/nextjs.md— for Next.js / React projects.cursor/checklist-templates/python.md— for Python / FastAPI projects.cursor/checklist-templates/go.md— for Go projects
Also load relevant guideline files to extract additional MUST/MUST NOT rules.
5. Check — Systematic Violation Scan
Review ALL changed files against the checklist items systematically:
- Read each changed file
- Check each checklist item against the actual code
- Record violations with: file, line number, rule ID, description
Important: Check ALL items, not just obvious ones. Security and naming rules are easy to miss.
6. Fix — Auto-Correct Violations
Skip this step if --dry-run is specified.
For each violation found:
- Fix the violation directly in the code
- Verify the fix doesn't break surrounding code
- Mark the item as fixed
Fix principles:
- Minimal changes — only fix what violates the checklist
- Preserve existing code style and formatting
- If a fix requires architectural changes (not a simple edit), flag it as ⚠️ manual review instead of auto-fixing
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 · 107 lines · 59 tokens per session scan A 22648321f087
ai-dev-os-check 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 59 tokens to every session and 895 once invoked, about $0.0003 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.
35-api-contracts
API versioning, contracts, and schema evolution rules.
45-environment-config
Environment configuration and secrets management rules.
50-rag-system
Retrieval-augmented generation rules.
55-data-model-versioning
Dataset versioning, model checkpoint management, and training reproducibility rules.