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 brcampidelli/chimera-agent --skill chimera-reproduce-before-diagnosinggit clone --depth 1 https://github.com/brcampidelli/chimera-agentWrote 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/brcampidelli/chimera-agent/chimera-reproduce-before-diagnosing)<a href="https://agentmods.dev/skills/brcampidelli/chimera-agent/chimera-reproduce-before-diagnosing"><img src="https://agentmods.dev/badge/skills/brcampidelli/chimera-agent/chimera-reproduce-before-diagnosing/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/brcampidelli/chimera-agent/chimera-reproduce-before-diagnosing"><img src="https://agentmods.dev/badge/skills/brcampidelli/chimera-agent/chimera-reproduce-before-diagnosing.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.00041 | $0.00989 |
| Opus 5 | $0.00020 | $0.00495 |
| Sonnet 5 | $0.00008 | $0.00198 |
| Haiku 4.5 | $0.00004 | $0.00099 |
Grade A, and why
chimera-reproduce-before-diagnosing 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 12d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Trigger
You are about to change code because of a failure you have not personally watched happen: a red CI job, a log excerpt in an issue, a user's description, or — the case this card is really about — a confident diagnosis handed to you by a reviewer, a sub-agent, or a static analysis tool, complete with a file and a line number.
It does not apply when the failure already is one command. A test that fails locally when you run it is a reproduction; do not build a second one. It also does not apply to work that has no failure in it — a new feature, a refactor, a design question. Those have nothing to reproduce.
Do
- Write the shortest thing that fails and can be run by itself: one script, one pytest node id, one CLI invocation. "Run the suite and look at the third error" is not it — you will read past the error every time.
- Run it. Copy the real output into your notes: the exception type, the wrong value next to the expected one, the exit code. Not your summary of it.
- Now state the diagnosis, and immediately try to kill it. Put a
raise RuntimeError("here")at the top of the function the diagnosis blames and rerun the reproduction. If the original failure still appears unchanged, that function is not on the failing path and the diagnosis is wrong regardless of how well argued it was. - Fix, rerun the same command, and keep the reproduction as a test in the same change. A repro that is deleted after the fix cannot tell you when the fix is reverted.
Avoid
Editing the frame of the traceback you recognise. The frame you recognise is the one you have read before, not the one that is wrong, and a plausible edit there will often make the symptom move somewhere else — which then reads as progress.
Avoid inheriting a diagnosis as a fact. A handed-over explanation is text, and the process that produces a fluent wrong explanation is the same process that produces a fluent right one, so the fluency carries no information about which you got. Treat it as a hypothesis with a name attached: useful for ordering what to try, worthless as evidence.
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.
- 12d ago First seen · 86 lines · 41 tokens per session scan A 9d70fa5a6199
chimera-reproduce-before-diagnosing is a skill published in the GitHub repository brcampidelli/chimera-agent (25 stars, last pushed today), licensed Apache-2.0. It adds 41 tokens to every session and 989 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-08-30.
Other skills, from other repositories
code-search
Search a codebase efficiently with ripgrep regular expressions, file globs, and git history search. Use to locate symbols, usages, and definitions instead of reading whole files.
code-review
Performs structured code review on a file or directory.
reframe-voice
Write, rewrite, or review content in the evidence-led reframe voice style. Use when the user explicitly asks to write in "reframe voice" or "reframe style". Do NOT use for general writing tasks.
systematic-debugging
Applies a modified Fagan Inspection methodology to resolve persistent bugs and complex issues. Use when several fix or debugging attempts have already failed and a methodical root-cause analysis warranting a Fagan inspection is needed. For first-pass diagnosis of a reproducible bug or regression use…
goal-flight-doctor
Use when the user invokes /goal-flight doctor or asks for Goal Flight readiness diagnostics on the current repository.
Docker Management
Manage Docker containers, images, volumes, networks, and Compose stacks — lifecycle ops, debugging, cleanup, and Dockerfile optimization.