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 validation-self-auditgit 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/validation-self-audit)<a href="https://agentmods.dev/skills/outlinedriven/odin-claude-plugin/validation-self-audit"><img src="https://agentmods.dev/badge/skills/outlinedriven/odin-claude-plugin/validation-self-audit.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.00053 | $0.00913 |
| Opus 5 | $0.00026 | $0.00456 |
| Sonnet 5 | $0.00011 | $0.00183 |
| Haiku 4.5 | $0.00005 | $0.00091 |
Grade A, and why
validation-self-audit 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 — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Validation self audit
Contract
| Field | Bound contract |
|---|---|
| Trigger | Before trusting a validation plan or result meant to show whether something worked, such as an A/B test, holdout, or score, or when its result looks too clean or self-confirming. |
| Authority | Read-only: inspect supplied validation design and evidence without changing files, VCS, credentials, paid services, published material, deployments, or remote state. |
| Side effect | None; names only the independence failures that fire and the corresponding fixes. |
| Done | Every firing pattern is named with an independence fix, patterns 3–5 are applied to the audit itself, and one root failure is identified instead of returning a laundry list. |
Inputs
- The validation claim, design, and observed result. Required.
- The intervention, baseline or control, sampling method, evaluator, metric, stopping rule, and raw evidence. Supply every item that exists; identify missing items rather than inventing them.
- An independent auditor's assessment. Optional; use it as the N=1 auditor check when available.
Procedure
- Bound the claim being validated, the intervention, the comparison, the measured outcome, and the decision the result is meant to support. Done when: the claim, intervention, comparison, outcome, and decision are all bounded.
- Trace independence through eight patterns: shared data between construction and evaluation; shared implementation between intervention and control; evaluator awareness of the expected result; metric selection after observing outcomes; optional stopping or selective reporting; contamination between treatment and holdout; dependence between observations presented as independent; and a benchmark or score that restates the system's own assumptions. Done when: every pattern is classified as firing, not firing, or unclassifiable.
- Report only patterns supported by supplied evidence. For each supported pattern, name the evidence and prescribe the smallest independence fix: a fresh holdout, separately implemented control, blinded evaluator, preregistered metric and stopping rule, contamination barrier, correct unit of analysis, or external ground truth. Done when: every firing pattern has evidence and a prescribed fix.
- Apply patterns 3–5 to this audit: check whether the auditor knows the desired verdict, chose criteria after seeing the result, or stopped after finding a convenient explanation. If any fires, mark the audit non-independent and prescribe its fix. Done when: the self-audit is complete and any non-independence is marked.
- When an independent assessment is available, compare it as an N=1 auditor check. Treat disagreement as evidence requiring resolution, not a majority vote. Done when: the N=1 comparison is completed or noted as unavailable.
- Identify the single root independence failure that best explains the supported findings. Keep secondary patterns only when they require a distinct fix. Done when: one root failure is identified.
- Stop with a blocked result when evidence needed to distinguish firing from non-firing patterns is unavailable; do not widen scope or infer clean validation from missing evidence. Done when: the blocked result names the exact missing artifact and unclassifiable patterns.
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 · 42 lines · 53 tokens per session scan A 2ed3a9401470
validation-self-audit is a skill published in the GitHub repository OutlineDriven/odin-claude-plugin (35 stars, last pushed yesterday), licensed Apache-2.0. It adds 53 tokens to every session and 913 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…