ai-dev-os-audit

ai-dev-os-audit is a cursor rule for coding agents from yunbow/ai-dev-os-plugin-cursor. It costs 34 tokens per session (434 once invoked), scanned A, original, MIT.

A periodic checkup for a project's four-layer AI development rules. It looks for broken dependencies between layers, outdated files, missing links, missing coverage, and conflicting rules.

In plain words
What is it for?
Use it monthly or quarterly to review rule files, check their update dates with Git, verify referenced files exist, and produce a health report with a score and layer-by-layer findings.
Why use it?
It helps find gaps and inconsistencies before they cause agents to follow incomplete or contradictory instructions. It also shows which guidance has not been reviewed recently.

Cursor rule

Install

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.

agentmods
npx agentmods add rules/yunbow/ai-dev-os-plugin-cursor/ai-dev-os-audit
Clone the repo
git clone --depth 1 https://github.com/yunbow/ai-dev-os-plugin-cursor

Wrote 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.

agentmods badge for ai-dev-os-audit

README.md
[![agentmods](https://agentmods.dev/badge/rules/yunbow/ai-dev-os-plugin-cursor/ai-dev-os-audit.svg)](https://agentmods.dev/rules/yunbow/ai-dev-os-plugin-cursor/ai-dev-os-audit)
Your own site
<a href="https://agentmods.dev/rules/yunbow/ai-dev-os-plugin-cursor/ai-dev-os-audit"><img src="https://agentmods.dev/badge/rules/yunbow/ai-dev-os-plugin-cursor/ai-dev-os-audit.svg" alt="Measured on agentmods" height="20"></a>
Per session 34 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 434 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00034 $0.00434
Opus 5 $0.00017 $0.00217
Sonnet 5 $0.00007 $0.00087
Haiku 4.5 $0.00003 $0.00043

Measured 3d ago against content hash 3b357a05c05b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

ai-dev-os-audit 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.

rules/ai-dev-os-audit.mdc · 60 lines

What it actually says

AI Dev OS 4-Layer Health Audit

Audit Items

1. Dependency Rules (Clean Architecture Principle)

  • Do L1 files contain tool-specific terms? ("Claude Code", "Cursor", "Next.js", etc.)
  • Do L2 files contain framework-specific implementation details?
  • Is the one-way dependency L1 → L2 → L3 → L4 maintained?

2. Expiration Check

  • L1: Last updated more than 5 years ago?
  • L2: Last updated more than 3 years ago?
  • L3: Last updated more than 12 months ago?
  • L4: Last updated more than 4 months ago?
  • Use git log to get the last update date for each file

3. Traceability

  • Does each L3 guideline have a link to an L2 principle?
  • Does each L4 AI Frame have a reference to an L3 guideline?
  • Are there orphaned rules (not linked to any principle)?

4. Coverage

  • Do all files referenced in .cursorrules actually exist?
  • Are there guidelines for the project's major file patterns?
  • Are there mapped guidelines for each directory under src/?

5. Consistency

  • Are there contradictory rules across multiple guidelines?
  • Are naming conventions consistent across all files?

Output Format

## AI Dev OS Health Audit Report

### Score: N/100

### Layer Health
| Layer | Files | Coverage | Freshness | Dependencies | Score |
|-------|-------|----------|-----------|-------------|-------|

### Issues Found
| Severity | Issue | Location | Action |
|----------|-------|----------|--------|

### Recommendations
1. [Priority: High] ...
2. [Priority: Medium] ...

Language

Respond in the same language as the project's .cursorrules file.

Changes

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.

  1. 3d ago First seen · 60 lines · 34 tokens per session scan A 3b357a05c05b

Subscribe to this mod's changes

ai-dev-os-audit 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 34 tokens to every session and 434 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.