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 agentmods add skills/outlinedriven/odin-claude-plugin/decidenpx skills add OutlineDriven/odin-claude-plugin --skill decidegit 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/decide)<a href="https://agentmods.dev/skills/outlinedriven/odin-claude-plugin/decide"><img src="https://agentmods.dev/badge/skills/outlinedriven/odin-claude-plugin/decide.svg" alt="Measured on agentmods" 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.00086 | $0.00585 |
| Opus 5 | $0.00043 | $0.00293 |
| Sonnet 5 | $0.00017 | $0.00117 |
| Haiku 4.5 | $0.00009 | $0.00059 |
Grade A, and why
decide 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 6d 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Decide
The user owns the pick, you own the framing and the execution. Two failure modes sit on either side: deciding for them, which is pov, and asking without ever acting, which is askme. This skill closes the seam between them, and nothing shipped does the whole loop, because askme, clarify, and brainstorm all terminate in an artifact while fix acts without asking.
Ground the fork before framing it
Resolve from evidence first with grep, glob, read, or lsp. A fork the code already answers is not a fork: read it, say what it answers, and do not ask. Never ask what a search settles.
Frame it
Question contract: skills/askme/SKILL.md:64-127. One single-select per axis, two to four options, (Recommended) first with the consequence in its description. Never multiSelect for override semantics, an antipattern spelled out at skills/askme/SKILL.md:68-101.
Options carry consequences, not labels
Each option names what the code looks like afterwards. Where two options differ visibly, put the difference in preview as a diff or a tree.
Take the pick and act in the same turn
A pick applied in one edit gets the edit. A pick needing a verify, keep, or revert loop goes to fix, with the pick restated as its goal. A pick that removes an observable surface or cannot be reverted from git gets one concern stated, then a yes.
Chained forks
When applying one pick opens the next, ask it immediately with the settled decision restated in one line. Never bank a queue of questions to fire at the end.
When the user picks what you would not
Execute the pick, state the concern once, never re-litigate.
Close
One line naming the fork, the pick, and what changed.
Boundaries
- A verdict of your own goes to
pov. - An exploration ending in a document goes to
askme. - A whole-session director-executor posture goes to
duet. - A wide design tree in batched rounds goes to
batch-ask-me. - Ambiguity inside a stated request rather than a fork goes to
clarify.
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.
- 6d ago First seen · 46 lines · 86 tokens per session scan A 1039e185479d
decide is a skill published in the GitHub repository OutlineDriven/odin-claude-plugin (35 stars, last pushed today), licensed Apache-2.0. It adds 86 tokens to every session and 585 once invoked, about $0.0004 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-08-30.
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…
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…