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 chipi/agentic-ai-homelab --skill repro-firstgit clone --depth 1 https://github.com/chipi/agentic-ai-homelabWrote 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/chipi/agentic-ai-homelab/repro-first)<a href="https://agentmods.dev/skills/chipi/agentic-ai-homelab/repro-first"><img src="https://agentmods.dev/badge/skills/chipi/agentic-ai-homelab/repro-first/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/chipi/agentic-ai-homelab/repro-first"><img src="https://agentmods.dev/badge/skills/chipi/agentic-ai-homelab/repro-first.svg" alt="Reviewed on agentmods" width="80" 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.00068 | $0.00373 |
| Opus 5 | $0.00034 | $0.00187 |
| Sonnet 5 | $0.00014 | $0.00075 |
| Haiku 4.5 | $0.00007 | $0.00037 |
Grade A, and why
repro-first 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 10d 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
repro-first
A real bug gets a failing test that reproduces it before the fix lands. The test is the regression guard for next time. No fix without a repro.
Steps
- Reproduce locally first. Pull evidence for THIS specific failure — the actual error, log, stack trace, or input. Don't theorize a root cause from "usually it's X"; get the real signal for this run.
- Write the failing test at the right layer — unit test, integration case, fixture, or a matrix row — that fails because of the bug. Run it; confirm it fails for the expected reason (red for the right cause, not a typo).
- Fix the code.
- Confirm green + no collateral. The new test passes, and the surrounding suite still passes — run the gate that covers the change, not the whole world.
- Keep the test. It ships with the fix in the same change. Don't delete it, don't mark it skip — it's the guard for the next regression.
Non-negotiables this enforces
- Real bug → repro before fix (rule #34): the failing test lands with the fix.
- Never invent root causes (rule #5): evidence for this run before a theory.
- Reproduce locally before pushing (rule #11).
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.
- 10d ago First seen · 30 lines · 68 tokens per session scan A aefb15e867a5
repro-first is a skill published in the GitHub repository chipi/agentic-ai-homelab (2 stars, last pushed 3d ago), licensed MIT. It adds 68 tokens to every session and 373 once invoked, about $0.0003 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-31.
Other skills, from other repositories
behavior-contract
Bug condition/postcondition formalization as testable Behavior Contracts. Defines invariants that must be preserved across fixes.
nw-bugfix
Bug fix workflow: root cause analysis → user review → regression test + fix via TDD.
debugging
A structured method for finding and fixing software bugs. It starts by writing a test that reproduces the failure, then investigates its underlying cause before making a small fix.
hk-rca
Interactive Root Cause Analysis enforcer. Guides you through the 7-step RCA protocol: Reproduce, Locate, Hypothesis, Failing Test, Fix, Verify Live, Document. Use when debugging a bug, investigating a failure, or when something unexpected happened. This skill gates each step — it won't let you skip to a fix without…
debug-flow
Systematic debugging workflow. Reproduce the issue, isolate root cause, write a failing test, fix, verify. Use when diagnosing bugs or unexpected behavior.
test-driven-bug-fix
Defines reproduce-red-green-refactor bug fixes. Load when correcting a defect with a regression test.