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 validate-changes-match-specsgit 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/validate-changes-match-specs)<a href="https://agentmods.dev/skills/outlinedriven/odin-claude-plugin/validate-changes-match-specs"><img src="https://agentmods.dev/badge/skills/outlinedriven/odin-claude-plugin/validate-changes-match-specs.svg" alt="Measured on agentmods" 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.00058 | $0.01912 |
| Opus 5 | $0.00029 | $0.00956 |
| Sonnet 5 | $0.00012 | $0.00382 |
| Haiku 4.5 | $0.00006 | $0.00191 |
Grade A, and why
validate-changes-match-specs 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 3d 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Validate changes match specs
Contract
| Field | Bound contract |
|---|---|
| Trigger | Resolving mismatches between specs and implementation. |
| Authority | Reversible local writes to named files only. Roll back any edit that diverges from a user-approved decision. |
| Side effect | Walks through mismatches and edits code or specs per user decisions. |
| Done | Summary states specs checked, mismatches resolved, files changed, validation run. |
Inputs
The skill reads the current branch diff and any specs present in the repository. No external services are required. Credentials, paid actions, publishing, deployment, and remote bulk mutation are not authorized. The user must supply a base branch or confirm the detected base when prompted.
Procedure
-
Identify changed files. Use
git merge-basewith the detected base branch andgit diff --name-only <base>...HEADto list all files introduced or modified by the current branch. Done when: every changed file is identified against the confirmed base. -
Discover specs. From the diff, find specs introduced or modified, especially under
specs/or matchingPRODUCT.md,TECH.md,SECURITY.md,MIGRATION.md,ROLLBACK.md,API.md,TESTING.md, orPRIVACY.md. Also check the PR description, commit messages, and branch name for referenced spec paths. If no relevant spec exists, stop and report that there is no spec to validate against. Done when: every relevant spec is found or the no-spec result is reported. -
Read specs. Read every relevant spec file completely before assessing implementation. Done when: every relevant spec has been read completely.
-
Extract commitments. From specs, PR descriptions, commit messages, and review comments, extract facts and commitments into categories:
- Product behavior: user-visible behavior, UX flows, success criteria, constraints, and edge cases.
- Technical implementation: files, components, APIs, data models, migrations, feature flags, architecture, dependencies, and rollout mechanics.
- Security and privacy: authentication, authorization, permission boundaries, secrets, data handling, logging, retention, abuse cases, and compliance claims.
- Validation: required tests, manual checks, CI commands, migration checks, and acceptance criteria.
- Non-goals: scope exclusions and intentionally deferred work.
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.
- 3d ago First seen · 133 lines · 58 tokens per session scan A 6c52493d706b
validate-changes-match-specs is a skill published in the GitHub repository OutlineDriven/odin-claude-plugin (35 stars, last pushed today), licensed Apache-2.0. It adds 58 tokens to every session and 1,912 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-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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…