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 using-agent-skillsgit 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/using-agent-skills)<a href="https://agentmods.dev/skills/plazmodium/odin-workflow/using-agent-skills"><img src="https://agentmods.dev/badge/skills/plazmodium/odin-workflow/using-agent-skills.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.00021 | $0.00740 |
| Opus 5 | $0.00010 | $0.00370 |
| Sonnet 5 | $0.00004 | $0.00148 |
| Haiku 4.5 | $0.00002 | $0.00074 |
Grade A, and why
using-agent-skills 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 3d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
using-agent-skills
Use skills as workflows, not reference material. Load only the skills needed for the current phase, then produce evidence before calling work complete.
Inspired by Addy Osmani's Agent Skills article: process over prose, anti-rationalization, verification, progressive disclosure, and scope discipline.
When To Use
- At the start of a session or slash command.
- When deciding which lifecycle workflow applies.
- When the task is expanding beyond the user's request.
Workflow
- Classify the work: define, plan, build, verify, review, simplify, or ship.
- Load the smallest relevant skill set for that phase.
- Surface important assumptions before acting.
- Stop and ask when requirements conflict or missing information materially changes the result.
- Push back when a request would reduce safety, correctness, maintainability, or reviewability.
- Prefer the boring, obvious solution.
- Touch only what the user asked you to touch.
- End with evidence: tests, typecheck, build, runtime trace, review findings, or a clear explanation of what was not verified.
Skill Router
| Situation | Load |
|---|---|
| Vague idea | idea-refine |
| Feature or significant change | spec-driven-development |
| Need implementable steps | planning-and-task-breakdown |
| Multi-file change | incremental-implementation |
| Behavior change or bug fix | test-driven-development |
| Framework/library uncertainty | source-driven-development |
| Poor output quality or stale context | context-engineering |
| High stakes or unfamiliar code | doubt-driven-development |
| User-facing UI | frontend-ui-engineering |
| API or boundary design | api-and-interface-design |
| Browser runtime behavior | browser-testing-with-devtools |
| Broken build/test/runtime | debugging-and-error-recovery |
| Pre-merge review | code-review-and-quality |
| Complex or clever code | code-simplification |
| Trust boundary, auth, secrets, external input | security-and-hardening |
| Performance target or regression | performance-optimization |
| VCS hygiene | git-workflow-and-versioning |
| Pipeline/deploy automation | ci-cd-and-automation |
| Removing or migrating old behavior | deprecation-and-migration |
| Architecture or API decision | documentation-and-adrs |
| Production launch | shipping-and-launch |
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.
- 3d ago First seen · 78 lines · 21 tokens per session scan A 594c5dd27e79
using-agent-skills is a skill published in the GitHub repository Plazmodium/odin-workflow (0 stars, last pushed 3mo ago), licensed MIT. It adds 21 tokens to every session and 740 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-03.
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.