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-reportgit 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-report)<a href="https://agentmods.dev/rules/yunbow/ai-dev-os-plugin-cursor/ai-dev-os-report"><img src="https://agentmods.dev/badge/rules/yunbow/ai-dev-os-plugin-cursor/ai-dev-os-report.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.00036 | $0.00253 |
| Opus 5 | $0.00018 | $0.00127 |
| Sonnet 5 | $0.00007 | $0.00051 |
| Haiku 4.5 | $0.00004 | $0.00025 |
Grade A, and why
ai-dev-os-report 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.
What it actually says
AI Dev OS Compliance Report Generation
Execution Flow
1. Determine Period
Determine the target period from the user's request (default: 1 week).
2. Collect Data
- Retrieve commits for the target period using
git log - Identify relevant guidelines for each changed file
- Aggregate past check results if available
3. Generate Report
## AI Dev OS Compliance Report
**Period**: YYYY-MM-DD — YYYY-MM-DD
### Summary
- Total commits: N
- Checked: N
- Compliance rate: N%
### Compliance Rate Trend
| Week | Compliance Rate | Violations | Main Violations |
|------|----------------|------------|-----------------|
### Major Violation Patterns
| Pattern | Occurrences | Guideline | Improvement Proposal |
|---------|-------------|-----------|---------------------|
### Improvement Proposals
1. ...
2. ...
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.
- 3d ago First seen · 46 lines · 36 tokens per session scan A 52bf2f132338
ai-dev-os-report 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 36 tokens to every session and 253 once invoked, about $0.0002 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.