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 OutlineDriven/odin-claude-plugin --skill spec-to-code-compliancegit 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/spec-to-code-compliance)<a href="https://agentmods.dev/skills/outlinedriven/odin-claude-plugin/spec-to-code-compliance"><img src="https://agentmods.dev/badge/skills/outlinedriven/odin-claude-plugin/spec-to-code-compliance/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/outlinedriven/odin-claude-plugin/spec-to-code-compliance"><img src="https://agentmods.dev/badge/skills/outlinedriven/odin-claude-plugin/spec-to-code-compliance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00066 | $0.01665 |
| Opus 5 | $0.00033 | $0.00833 |
| Sonnet 5 | $0.00013 | $0.00333 |
| Haiku 4.5 | $0.00007 | $0.00167 |
Grade A, and why
spec-to-code-compliance 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.
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.
Spec to code compliance
Contract
| Field | Bound contract |
|---|---|
| Trigger | Implementation must be checked path-by-path against an authoritative specification, whitepaper, standard, or design document; or during PR review when checked-in spec context exists in the repository and the implementation must be compared against it. |
| Authority | Reversible-local: local files and searches only; no remote mutation, no credential exposure, no deployment. For PR-review mode, fold findings into review.json only; no GitHub posts, no separate report file. |
| Side effect | Per-requirement evidence records, refuted or confirmed divergence findings, reverse undocumented-behavior analysis, coverage caveats, and (in PR-review mode) spec-drift findings folded into review.json. |
| Done | Each selected requirement has one grounded verdict with searches and lines read, divergences survive independent refutation, and unchecked or unreadable scope is explicit. In PR-review mode, review.json contains material spec-drift findings or an explicit close-match. |
Inputs
Required:
spec: authoritative specification, whitepaper, standard, or design document. Accepts a file path, URL, or pasted text. In PR-review mode, this is the checked-inspec_context.mdor equivalent spec file.implementation: the codebase or source files to audit. Accepts a directory path or file list. In PR-review mode, this is the PR diff and checked-out branch contents.
Optional:
requirements: subset of spec requirements to verify; defaults to all extractable requirements.coverage: percentage or section target; defaults to 100 percent of stated requirements.divergence_thresholds: minimum evidence count to confirm a divergence; defaults to two independent reads.pr_description.md(PR-review mode only): additional scope or rationale.
Refusal
- Missing spec: stop. Report "No specification provided."
- Unreadable spec: stop. Report the file or URL that could not be read.
- Zero requirements extracted: stop. Report "Could not extract verifiable requirements from specification."
- Missing implementation: stop. Report "No implementation provided."
- Empty audit scope: stop. Report "No requirements in scope for audit."
- All requirements unchecked: fail. Report "Audit could not verify any requirement."
- Missing spec context (PR-review mode): the skill does not route. Stop without writing
review.json.
What ships with it
1 file 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.
- 4d ago First seen · 79 lines · 66 tokens per session scan A 99f9d52d0cfb
spec-to-code-compliance is a skill published in the GitHub repository OutlineDriven/odin-claude-plugin (35 stars, last pushed yesterday), licensed Apache-2.0. It adds 66 tokens to every session and 1,665 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…