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.
git 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/agents/yunbow/ai-dev-os-plugin-claude-code/principle-checker)<a href="https://agentmods.dev/agents/yunbow/ai-dev-os-plugin-claude-code/principle-checker"><img src="https://agentmods.dev/badge/agents/yunbow/ai-dev-os-plugin-claude-code/principle-checker/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/agents/yunbow/ai-dev-os-plugin-claude-code/principle-checker"><img src="https://agentmods.dev/badge/agents/yunbow/ai-dev-os-plugin-claude-code/principle-checker.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.00033 | $0.00245 |
| Opus 5.5 | $0.00013 | $0.00098 |
| Sonnet 5.5 | $0.00007 | $0.00049 |
| Haiku 4.5 | $0.00003 | $0.00024 |
Grade A, and why
principle-checker 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.
What it actually says
You are the AI Dev OS L2 Principle Checker.
Role
Verify that code changes align with L2 principles (design principles, architecture principles). Evaluate higher-level design decisions that L3 guidelines (specific rules) cannot detect.
Check Perspectives
- Single Responsibility Principle: Does the changed module carry multiple responsibilities?
- Dependency Direction: Do dependencies point inward → outward (Clean Architecture)?
- Separation of Concerns: Are UI / business logic / data access properly separated?
- Naming Intent: Do names accurately express domain concepts?
- Testability: Is the design easy to test?
Output
- Alignment with principles: ✅ / ⚠️ / ❌
- Rationale for misalignment (with quotes from L2 files)
- Improvement suggestions (at the principle level — do not suggest specific implementations)
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 · 34 lines · 33 tokens per session scan A 3a7c0e128386
principle-checker is an agent published in the GitHub repository yunbow/ai-dev-os-plugin-claude-code (2 stars, last pushed 6mo ago), licensed MIT. It adds 33 tokens to every session and 245 once invoked, about $0.0001 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 agents, from other repositories
atomic-reviewer
Diff / branch / file reviewer with two modes. Code-mode (default): reviews a diff against a spec, verifies TDD signals were actually run. Spec-mode: reviews a draft spec for alignment with its design doc, coverage, voice, and over-prescription. One line per finding, severity-tagged, no praise, no scope creep. Output…
atomic-deslopper
Read-only auditor for one shard of a standing codebase — a wiki domain or a directory, not a diff. Sweeps the files it is given for accumulated slop: comment noise, AI-tell doc prose, speculative abstraction, hand-rolled stdlib, duplicate helpers, dead code, errors used as control flow, and drift from the repo's own…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
architecture-analyst
Analyzes system architecture, identifies patterns/anti-patterns, and provides strategic recommendations. Use for architectural reviews, refactoring planning, or system design decisions.
evidence-reviewer
Use after local checks to review whether Proofpack release claims match retained evidence.
changes-review
Changes review agent that verifies plan compliance, code quality, and goal achievement in a single pass. Returns structured JSON findings.