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 behavior-validatorgit 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/behavior-validator)<a href="https://agentmods.dev/skills/outlinedriven/odin-claude-plugin/behavior-validator"><img src="https://agentmods.dev/badge/skills/outlinedriven/odin-claude-plugin/behavior-validator/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/behavior-validator"><img src="https://agentmods.dev/badge/skills/outlinedriven/odin-claude-plugin/behavior-validator.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00059 | $0.01007 |
| Opus 5.5 | $0.00024 | $0.00403 |
| Sonnet 5.5 | $0.00012 | $0.00201 |
| Haiku 4.5 | $0.00006 | $0.00101 |
Grade A, and why
behavior-validator 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 1mo 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.
This is a copy
100% identical to behavior-validator — 9 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Behavior validator
Contract
| Field | Bound contract |
|---|---|
| Trigger | User needs a code-review-agnostic skill to validate a web app, CLI, API, or generated artifact against a source-blind behavior contract, or as a black-box companion to a code-aware review |
| Authority | Read-only. No file, VCS, credential, paid, published, deployed, or remote mutation. Reads only the runtime output of the target; never reads source code, repository state, or build internals |
| Side effect | Produces a structured behavior validation report. No mutation of the target, source, or workspace beyond emitting the report |
| Done | Every contract clause has an observable result; the report correctly reflects real-time behavior and no implementation evidence contaminated the validation |
Inputs
- A behavior contract: a list of clauses, each with an identifier, a stimulus, and an expected observable outcome. Must be supplied.
- A target descriptor: how to reach the subject — a URL, a CLI invocation, an API endpoint, or an artifact path. Must be supplied.
- Optional: authentication material (tokens, headers), environment variables, seed data, or a run budget.
- Source code, repository state, and build internals are never inputs and must not be read.
Procedure
- Parse the contract into clauses. Reject any clause whose expected outcome references source structure (file names, function names, internal types, line numbers) — mark it out-of-scope, because source-blind validation cannot observe implementation structure. Done when: all clauses are parsed and source-referencing clauses are marked out-of-scope.
- Establish source-blind isolation for the whole run: do not read, list, grep, or otherwise inspect source files, repository state, or build internals. Operate only against the target's runtime surface. Done when: source-blind isolation is established and maintained.
- For each in-scope clause, construct a probe from its stimulus: an HTTP request, a CLI invocation, an API call, or an artifact inspection limited to observable output. Done when: every in-scope clause has a constructed probe.
- Apply anti-cheat probes per clause: re-run the stimulus with perturbed and edge inputs (empty, oversized, malformed, reordered, boundary values) to distinguish genuine behavior from hardcoded or coincidental outputs. Record whether the outcome is stable across the perturbations. Done when: every clause has its anti-cheat stability flag recorded.
- Execute each probe against the live target and capture only the observable result (status code, headers, stdout/stderr, exit code, rendered output). Redact secrets and personally identifying information from every captured evidence excerpt. Done when: every probe is executed with redacted evidence captured.
- Classify each clause: pass (observed outcome matches the expected outcome), fail (observable mismatch), blocked (target unreachable or probe could not execute), out-of-scope (clause not observable from the runtime surface). Done when: every clause has its classification assigned.
- Assemble the report mapping each probe category to its clause result, attaching the redacted evidence excerpt and the anti-cheat stability flag. Done when: the report maps every clause to its result with evidence and stability flag.
- Stop. Do not widen scope, patch the target, read source to explain a result, or infer an expected outcome the contract did not state. Done when: the report is emitted and no scope widening, patching, or source reading occurred.
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.
- 1mo ago First seen · 45 lines · 59 tokens per session scan A 7306aac17161
behavior-validator is a skill published in the GitHub repository OutlineDriven/odin-claude-plugin (37 stars, last pushed 21d ago), licensed Apache-2.0. It adds 59 tokens to every session and 1,007 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to behavior-validator, differing in 9 lines, and is treated as a copy.
Other skills, from other repositories
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…