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 reproduce-and-fix-issuesgit 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/reproduce-and-fix-issues)<a href="https://agentmods.dev/skills/outlinedriven/odin-claude-plugin/reproduce-and-fix-issues"><img src="https://agentmods.dev/badge/skills/outlinedriven/odin-claude-plugin/reproduce-and-fix-issues/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/reproduce-and-fix-issues"><img src="https://agentmods.dev/badge/skills/outlinedriven/odin-claude-plugin/reproduce-and-fix-issues.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.00033 | $0.00882 |
| Opus 5 | $0.00016 | $0.00441 |
| Sonnet 5 | $0.00007 | $0.00176 |
| Haiku 4.5 | $0.00003 | $0.00088 |
Grade A, and why
reproduce-and-fix-issues 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 5d 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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reproduce and fix issues
Contract
| Field | Bound contract |
|---|---|
| Trigger | Reproduce and fix a trusted bug or performance report. |
| Authority | Human-gated: asks before credentials, data-at-rest changes, paid actions, publishing, deployment, remote bulk mutation, or irreversible deletion (preview target and consequence); otherwise reversible local: writes only the fix and reproduction evidence; rollback is version control. No remote mutation except the human-approved draft PR. |
| Side effect | Drives the application under test, captures reproduction evidence, and may open one draft PR. No other remote operations. |
| Done | Verified operational-thread outcome with cleanup. |
Refusals
- Untrusted reports: rejected. The report must name the affected feature, the environment, and the expected versus actual behavior.
- Scope beyond the named feature: rejected. Do not extend the fix to adjacent features or infrastructure without an explicit new report.
- Assuming a race condition without at least two independent reproduction attempts: rejected. Fail the reproduction step instead.
Inputs
- Required: a trusted bug or performance report describing the symptom or regression. The report must name the affected feature, the environment or context, and the expected versus actual behavior.
- Optional: reproduction steps, a stack trace, a performance profile, or any supplemental diagnostic from the report.
Procedure
- Accept the trusted report. Confirm the affected feature, environment, and symptom are identifiable. Stop if the report does not name a feature or an observable failure mode. Done when: the feature, environment, and symptom are confirmed identifiable.
- Drive the application in the environment described by the report. Reproduce the exact symptom before proceeding. Done when: the symptom is reproduced.
- Capture reproduction evidence: console output, error messages, stack traces, timing data, or screenshots that record the failure. Fail the reproduction step if the symptom cannot be reproduced after at least two independent attempts; do not assume a race condition. Done when: evidence is captured or
no-reprois returned. - Identify the root cause within the affected feature's code. Trace the failure to the first invariant violation or unexpected state. Do not widen scope beyond the named feature. Done when: the root cause is identified.
- Implement the minimal fix that resolves the root cause. Validate that the fix does not introduce a new failure in the surrounding behavior. Done when: the fix is implemented and surrounding behavior is validated.
- Verify the fix resolves the reproduction case: repeat the reproduction steps and confirm the symptom no longer occurs. Done when: the symptom no longer occurs on repetition.
- Clean up any temporary artifacts created during reproduction or diagnosis. If the fix is verified and human approval is given, open one draft PR against the relevant branch. If approval is withheld, retain the verified fix locally and stop without publishing. Done when: cleanup is done and the PR is opened or the fix is retained locally.
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.
- 5d ago Changed · -22 tokens per session 8a4c64bc6528
- 7d ago First seen · 50 lines · 55 tokens per session scan A e6156445f247
reproduce-and-fix-issues is a skill published in the GitHub repository OutlineDriven/odin-claude-plugin (35 stars, last pushed 2d ago), licensed Apache-2.0. It adds 33 tokens to every session and 882 once invoked, about $0.0002 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-04.
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…
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
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…