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 skills/yunbow/ai-dev-os-plugin-claude-code/ai-dev-os-whynpx skills add yunbow/ai-dev-os-plugin-claude-code --skill ai-dev-os-whygit clone --depth 1 https://github.com/yunbow/ai-dev-os-plugin-claude-codeWrote 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/skills/yunbow/ai-dev-os-plugin-claude-code/ai-dev-os-why)<a href="https://agentmods.dev/skills/yunbow/ai-dev-os-plugin-claude-code/ai-dev-os-why"><img src="https://agentmods.dev/badge/skills/yunbow/ai-dev-os-plugin-claude-code/ai-dev-os-why.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.00057 | $0.00346 |
| Opus 5 | $0.00028 | $0.00173 |
| Sonnet 5 | $0.00011 | $0.00069 |
| Haiku 4.5 | $0.00006 | $0.00035 |
Grade A, and why
ai-dev-os-why 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 5d 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 "Why This Rule?" Explainer
Execution Flow
1. Parse the User's Question
Identify the relevant L3 guideline rule from the question.
(e.g., "Why is any prohibited?" → the any-related rule in common/code.md)
2. Load L3 Guideline
Retrieve the relevant rule and its context.
3. Reference L2 Principles
- Find the principle referenced by the guideline (via traceability links)
- If no link exists, infer from content
4. Reference L1 Philosophy
Identify the philosophical value that the principle is rooted in.
5. Provide Examples
- Concrete examples of what happens without this rule
- Before/After code snippets
Output Format
📖 Rule: [Rule content]
📁 Source: [Guideline file]
🔗 Traceability:
L3 Guideline → [Specific rule]
L2 Principle → [Supporting principle]
L1 Philosophy → [Underlying value]
💡 Without this rule:
[Description of specific risks or problems]
📝 Before/After:
[Code examples]
Language
Respond in the same language as the project's CLAUDE.md 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.
- 5d ago First seen · 60 lines · 57 tokens per session scan A 09c989124e9d
ai-dev-os-why is a skill published in the GitHub repository yunbow/ai-dev-os-plugin-claude-code (2 stars, last pushed 5mo ago), licensed MIT. It adds 57 tokens to every session and 346 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 skills, from other repositories
guideline-checker
Automatically check whether git diff contents comply with project guidelines after code changes. Run at coding completion or before committing.
type-check
Run TypeScript type checking and ESLint, identify error locations, and provide fix suggestions. Used for quality assurance after implementation.
stale-brain
Audit AI agent memory and instruction files: CLAUDE.md, AGENTS.md, .cursorrules, GEMINI.md, copilot-instructions.md and every other major agent's memory files (13 agents, 18+ file locations) against the live repository. Use when the user runs /stale-brain or asks to audit, verify, refresh, lint, or fix agent memory…
project-spine-kickoff
Use when the user wants to set up Project Spine for a new project — phrases like "new client project", "kickoff", "create AGENTS.md from scratch", "generate agent instructions for this repo", "set up project context". Runs spine init → edits brief → spine compile → reviews outputs. For stale files use…
project-spine
Use when the user mentions AGENTS.md, CLAUDE.md, copilot-instructions, Cursor rules, project brief, context for coding agents, agency kickoff, onboarding a new project, or asks "how do I set up Project Spine". This is the orientation skill — reach for it FIRST when the user's intent involves Project Spine, then chain…
project-spine-drift
Use when the user mentions drift, says AGENTS.md / CLAUDE.md / copilot-instructions / Cursor rules are "stale" or "out of date", asks about CI catching docs drift, or says "check if my spine is still current". Runs spine drift check, interprets each drift category, and guides resolution. For initial setup use…