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 Plazmodium/odin-workflow --skill idea-refinegit clone --depth 1 https://github.com/Plazmodium/odin-workflowWrote 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/plazmodium/odin-workflow/idea-refine)<a href="https://agentmods.dev/skills/plazmodium/odin-workflow/idea-refine"><img src="https://agentmods.dev/badge/skills/plazmodium/odin-workflow/idea-refine.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.00017 | $0.00301 |
| Opus 5 | $0.00009 | $0.00151 |
| Sonnet 5 | $0.00003 | $0.00060 |
| Haiku 4.5 | $0.00002 | $0.00030 |
Grade A, and why
idea-refine 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.
What it actually says
idea-refine
When To Use
- The user has a rough concept, not a concrete request.
- Goals, users, constraints, or success criteria are unclear.
- Several possible solutions could satisfy the request.
Workflow
- Restate the idea in one sentence.
- Identify the target user, problem, and desired outcome.
- List constraints, non-goals, risks, and unknowns.
- Generate 2-3 plausible solution shapes.
- Compare tradeoffs briefly.
- Recommend the smallest viable direction.
- Ask only the questions needed to unblock a spec or implementation.
Anti-Rationalization
| Excuse | Rebuttal |
|---|---|
| "The idea is obvious." | Obvious ideas often hide conflicting success criteria. |
| "I should start coding to discover the shape." | Discovery code becomes accidental product code. Clarify first. |
| "Asking questions slows things down." | One precise question is cheaper than building the wrong thing. |
Verification
- The proposal names the user, problem, outcome, constraints, and non-goals.
- Open questions are explicit.
- The recommended direction is smaller than the broadest possible solution.
Exit Criteria
- The user or agent can write a spec with clear acceptance criteria.
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 · 43 lines · 17 tokens per session scan A d1ea8eff0e9b
idea-refine is a skill published in the GitHub repository Plazmodium/odin-workflow (0 stars, last pushed 3mo ago), licensed MIT. It adds 17 tokens to every session and 301 once invoked, about $0.0001 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-01.
Other skills, from other repositories
b123d-modeling
Use this skill when asked to model, build, or modify a 3D part or assembly with build123d — from a text description, a technical drawing (image or PDF), dimensions in a spec, or an existing STEP/STL file.
b123d-edit
Use this skill when the task is to change an existing build123d model or script: "make this bracket 5 mm taller", "move the holes inward", "add a counterbore", "remove this rib", "make it fit this mating part", or "repair the code so the intended edit remains parametric".
new-gh-issue-orchestration
Orchestrates a GitHub-issue-driven delivery workflow from issue intake to PR creation using reviewer-first then worker execution. Invoked when the user provides a GitHub issue link/number and asks to start end-to-end delivery.
hmem-release
Pre-publish checklist for hmem: skills synced, version bumped, tests green, nothing forgotten. Use before npm publish or when the user says 'release', 'publish', 'push a release', or 'neue Version'.
mlflow-traces
Use when working with MLflow traces: debugging via MCP tools, analyzing performance, logging feedback, writing custom scorers/evaluations, or cleaning up trace data.
video-explainer
Teaches Claude how to use the 15 video explainer tools to create explainer videos from research content. Activates when working with video synthesis, explainer creation, or the video-explainer MCP server.