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 agents/yunbow/ai-dev-os-plugin-claude-code/principle-checkergit 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.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.00033 | $0.00245 |
| Opus 5 | $0.00016 | $0.00122 |
| Sonnet 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 4d 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.
- 4d 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 5mo ago), licensed MIT. It adds 33 tokens to every session and 245 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 agents, from other repositories
gsd-executor
Executes GSD plans with atomic commits, deviation handling, checkpoint protocols, and state management. Spawned by execute-phase orchestrator or execute-plan command.
document-steward
GOAL: One document per domain. Minimum tokens for maximum clarity.
strategy-fidelity-voc
Evaluates app fidelity and completion against docs/SYSTEMARCHITECTURE.md and domain references. Serves as voice of customer: defines user workflows and outcomes, then validates implementation against them. Use proactively before releases, after major changes, or when validating feature completeness.
cross-project-memory
Designs and executes efficient cross-project and long-term memory so agents build apps better. Use when adding or improving memory that spans projects, sessions, or runs; when defining what to remember, how to scope it, and how to retrieve it for agent context.
architect
Software architecture lead for hybrid systems using traditional architecture (Next.js + PostgreSQL) and AI-agent-supportive architecture (ruvector). Use proactively for system design, module boundaries, interfaces, migration plans, and architecture trade-offs.
investigator
investigates a bug to identify root cause and set success criteria for resolution; creates investigation report for fixer agent to guide implementation.