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 skills add yunbow/ai-dev-os-plugin-claude-code --skill ai-dev-os-initgit 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-init)<a href="https://agentmods.dev/skills/yunbow/ai-dev-os-plugin-claude-code/ai-dev-os-init"><img src="https://agentmods.dev/badge/skills/yunbow/ai-dev-os-plugin-claude-code/ai-dev-os-init/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/yunbow/ai-dev-os-plugin-claude-code/ai-dev-os-init"><img src="https://agentmods.dev/badge/skills/yunbow/ai-dev-os-plugin-claude-code/ai-dev-os-init.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00045 | $0.00652 |
| Opus 5.5 | $0.00018 | $0.00261 |
| Sonnet 5.5 | $0.00009 | $0.00130 |
| Haiku 4.5 | $0.00005 | $0.00065 |
Grade A, and why
ai-dev-os-init 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 1mo 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Dev OS Setup Wizard
Execution Flow
1. Interview the User
- Tech stack (Next.js / Python / Go / etc.)
- Project scale (personal / team / enterprise)
- Existing rule files (.cursorrules, CLAUDE.md, .kiro/steering/, etc.)
2. Detect and Import Existing Rules
Scan the project for existing configuration and rule files:
| Source | Action |
|---|---|
.cursorrules |
Convert to L3 guidelines |
Existing CLAUDE.md |
Classify into L3-L4 |
.editorconfig |
Import formatting rules into L3 common/code.md |
.eslintrc / eslint.config.* |
Extract coding rules into L3 guidelines |
biome.json / biome.jsonc |
Extract lint/format rules into L3 guidelines |
ruff.toml / pyproject.toml [tool.ruff] |
Extract Python lint rules into L3 guidelines |
.prettierrc / prettier.config.* |
Import formatting config into L3 common/code.md |
tsconfig.json (strict settings) |
Reference in L3 common/code.md |
.github/workflows/*.yml |
Reference CI/CD patterns in L3 common/cicd.md |
For each detected file:
- Read its content
- Extract rules that map to AI Dev OS guideline categories
- Present the extracted rules to the user for confirmation
- Write confirmed rules into the appropriate L3 guideline files
3. Generate Templates
Generate the following structure:
ai-dev-os/
├── 01_philosophy/
│ └── core-values.md # Minimal placeholder
├── 02_decision-criteria/
│ └── coding.md # 5-10 basic principles
├── 03_guidelines/
│ ├── common/
│ │ ├── code.md # Basic rules based on tech stack
│ │ ├── naming.md
│ │ └── security.md
│ └── frameworks/
│ └── [selected-stack]/
│ └── overview.md
└── 04_ai-frames/
└── claude-code.md # CLAUDE.md reference pattern
4. Generate CLAUDE.md
- Auto-insert references to the ai-dev-os directory
- Set up Specificity Cascade
5. Git Submodule Setup (Optional)
- For managing ai-dev-os as a separate repository
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.
- 1mo ago First seen · 79 lines · 45 tokens per session scan A da7840f0776f
ai-dev-os-init is a skill published in the GitHub repository yunbow/ai-dev-os-plugin-claude-code (2 stars, last pushed 7mo ago), licensed MIT. It adds 45 tokens to every session and 652 once invoked, about $0.0002 per session on Opus 5.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.
memstack-deployment-domain-ssl
Use this skill when the user says 'setup domain', 'configure DNS', 'SSL certificate', 'domain-ssl', 'custom domain', 'HTTPS setup', or needs to configure DNS records, SSL certificates, and custom domains for any hosting provider. Do NOT use for full deployment workflows.
memstack-development-refactor-planner
Use this skill when the user says 'refactor', 'refactoring plan', 'code cleanup', 'reduce duplication', 'simplify code', 'tech debt', 'god class', 'tight coupling', or needs to systematically improve existing code. Identifies targets, assesses risk, and builds incremental execution plans. Do NOT use for writing new…
memstack-product-feedback-analyzer
Use this skill when the user says 'analyze feedback', 'feedback analysis', 'what are customers asking for', or has support tickets, reviews, or survey data to categorize, score, and prioritize into actionable reports. Do NOT use for competitor analysis or market research.
memstack-seo-meta-tag-optimizer
Use this skill when the user says 'meta tags', 'title tag', 'meta description', 'optimize meta', 'SERP preview', or needs to write or optimize HTML meta tags for better search visibility and click-through rates. Do NOT use for schema markup or full site audits.