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/outlinedriven/odin-claude-plugin/principlesnpx skills add OutlineDriven/odin-claude-plugin --skill principlesgit clone --depth 1 https://github.com/OutlineDriven/odin-claude-pluginWrote 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/outlinedriven/odin-claude-plugin/principles)<a href="https://agentmods.dev/skills/outlinedriven/odin-claude-plugin/principles"><img src="https://agentmods.dev/badge/skills/outlinedriven/odin-claude-plugin/principles.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.00061 | $0.02546 |
| Opus 5 | $0.00030 | $0.01273 |
| Sonnet 5 | $0.00012 | $0.00509 |
| Haiku 4.5 | $0.00006 | $0.00255 |
Grade A, and why
principles 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 yesterday.
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 — 226 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Principles
Indexed anchor register: 21 named principles, each a law plus the moment it bites. Read the index, jump to the anchor, apply the law. Principles governs judgment only and never executes or mutates. When an anchor requires mutation or execution, route the user to the owning skill (fix, debug, architect, deslop, commit, ci-cd) instead of instructing execution. Come here to decide, not to run a repair.
Five anchors carry procedure-dense references (linked inline); the rest are complete at anchor length.
Contract
| Field | Bound contract |
|---|---|
| Trigger | A request names a working principle by name or example, or asks which principle governs a decision. |
| Authority | Read-only. Names the owning skill for execution; never mutates files, VCS, credentials, or remote state. |
| Side effect | Guidance in chat output only. No file, VCS, credential, paid, published, deployed, or remote mutation. |
| Done | The governing principle is named with its law and bite point, and the owning skill is named when the anchor requires execution. |
Index
| Anchor | Governs |
|---|---|
| Subtract before you add | land deletions first, as their own commit |
| Sequence verifiable units | per-unit checks, halt at first failure |
| Outcome-oriented execution | plan → rollback-anchor migration |
| Migrate callers, then delete | one-wave API replacement |
| Redesign from first principles | requirement integration without bolt-ons |
| Build the lever | hand-do one, codify, rerun |
| Idempotent operations | retries converge to one state |
| Encode lessons in structure | repeated instruction → enforcement artifact |
| Fix root causes | why-chain over symptom patching |
| Prove it works | captured evidence from the real artifact |
| Model the domain | typed state machines, illegal states fail compile |
| Type system discipline | compiler as the proof of constraints |
| Foundational thinking | types before logic |
| Boundary discipline | validate once, at the seam |
| Separate before serializing | per-actor state before locks |
| Laziness protocol | deletion-first smallest change |
| Minimize reader load | one-pass state trace |
| Experience first | fewer polished over many partial |
| Exhaust the design space | 3+ distinct alternatives, criteria first |
| Never block on the human | reversible proceeds, irreversible parks |
| Guard the context window | decisions in context, payload out |
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday First seen · 226 lines · 61 tokens per session scan A ffa4534f6332
principles is a skill published in the GitHub repository OutlineDriven/odin-claude-plugin (35 stars, last pushed yesterday), licensed Apache-2.0. It adds 61 tokens to every session and 2,546 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-09-04.
Other skills, from other repositories
java-clean-arch
Reviews or implements Clean Architecture / Hexagonal Architecture (Ports & Adapters) and DDD tactical patterns for Java projects. Use when user asks to "apply clean architecture", "implement hexagonal architecture", "add ports and adapters", "apply DDD", "refactor to clean arch", "review architecture", or "add value…
java-adr
Creates, lists, and manages Architecture Decision Records for Java projects. Use when user asks to "create an ADR", "document this decision", "write an architecture decision", "add ADR", "list decisions", "show ADRs", or "record this architectural choice".
java-test
Generates JUnit 5 and Mockito unit tests or Testcontainers integration tests, auto-detecting project setup. Use when user asks to "write tests", "generate tests", "add unit tests", "create test class", "test this service", or "write integration tests".
java-jpa
Reviews Spring Data JPA for N+1 queries, fetch strategies, projections, and Specifications. Use when user asks to "review JPA", "check for N+1", "JPA performance", "review my entities", "check fetch strategy", or "review my repositories".
java-logging
Reviews Java logging for SLF4J best practices, MDC context, structured logging, and PII safety. Use when user asks to "review logging", "check my logs", "logging review", "is my logging correct", "MDC setup", or "check for PII in logs".
java-security
Reviews or implements Spring Security configuration — JWT authentication, OAuth2, method-level security, CORS, and CSRF. Use when user asks to "add authentication", "secure this API", "implement JWT", "configure Spring Security", "add OAuth2 login", "protect endpoints", or "review security config".