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 fromzerogit 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/fromzero)<a href="https://agentmods.dev/skills/outlinedriven/odin-claude-plugin/fromzero"><img src="https://agentmods.dev/badge/skills/outlinedriven/odin-claude-plugin/fromzero/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/fromzero"><img src="https://agentmods.dev/badge/skills/outlinedriven/odin-claude-plugin/fromzero.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.00042 | $0.00718 |
| Opus 5.5 | $0.00017 | $0.00287 |
| Sonnet 5.5 | $0.00008 | $0.00144 |
| Haiku 4.5 | $0.00004 | $0.00072 |
Grade A, and why
fromzero 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.
How it starts
The opening of the file, as written. The whole thing — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fromzero
Contract
| Field | Bound contract |
|---|---|
| Trigger | The user wants to replace a greenfield attempt with a clean pad carrying only proven requirements. |
| Authority | Human-gated: requires explicit human invocation before acting; otherwise reversible local: writes only VCS-tracked targets (show the exact set before mutation); rollback is version control. No remote mutation. |
| Side effect | A new greenfield attempt on a clean pad; the old attempt remains recoverable through VCS. |
| Done | A new greenfield attempt exists carrying only verified requirement statements, and the old attempt is reachable in VCS history. |
Not for
- Rebuilding a design from primitives: use from-first-principle.
- Continuing an existing attempt with fixes: this replaces, it does not patch.
- Operating without a committed, VCS-recoverable current attempt: the old attempt must survive in history.
Inputs
- The current greenfield attempt, which must be under version control and committed.
- A list of proven requirements. A requirement is proven only when it has been verified (tested, accepted, or otherwise demonstrated). Speculative or unverified scope is not proven.
Procedure
-
Verify the current attempt is committed and recoverable through version control. If any uncommitted or untracked work exists, stop and require the human to commit or discard it first. Done when: the working tree is clean and the attempt is in VCS history.
-
Filter requirements to verified only. Carry only requirements that have been verified; discard unproven, speculative, or accumulated scope. Done when: the proven-requirements set is listed and each entry is verified.
-
Branch from the recoverable commit to clear the working surface. Before any mutation, list the exact set of VCS-tracked targets the clearance will delete (the tracked files of the old attempt) and show that set; the mutation is a branch creation followed by the clearance of exactly those listed targets. The old attempt survives in VCS history while the working surface is cleared on the new branch. Do not use an unspecified reset alternative. Done when: the exact target set was shown before mutating, the working surface is clear on the new branch, and the old attempt is reachable in VCS.
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 Changed · -16 tokens per session f8a359bf2f13
- 1mo ago First seen · 49 lines · 58 tokens per session scan A 2a92e32869e0
fromzero is a skill published in the GitHub repository OutlineDriven/odin-claude-plugin (37 stars, last pushed 21d ago), licensed Apache-2.0. It adds 42 tokens to every session and 718 once invoked, about $0.0002 per session on Opus 5.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
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…