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-carry-the-failure-forwardgit 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-carry-the-failure-forward)<a href="https://agentmods.dev/skills/brcampidelli/chimera-agent/chimera-carry-the-failure-forward"><img src="https://agentmods.dev/badge/skills/brcampidelli/chimera-agent/chimera-carry-the-failure-forward/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-carry-the-failure-forward"><img src="https://agentmods.dev/badge/skills/brcampidelli/chimera-agent/chimera-carry-the-failure-forward.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.00044 | $0.01271 |
| Opus 5 | $0.00022 | $0.00635 |
| Sonnet 5 | $0.00009 | $0.00254 |
| Haiku 4.5 | $0.00004 | $0.00127 |
Grade A, and why
chimera-carry-the-failure-forward 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Trigger
You have a loop that runs an attempt, judges it, and runs another one with feedback: an agent with a verifier, a code fixer against a test suite, a generate-and-check pipeline. The budget is more than two attempts, and the workspace is reverted between them so each attempt starts clean.
It does not apply to an idempotent retry over a flaky transport — a network call that failed for reasons unrelated to what you sent. There is nothing to learn from attempt 1 there, and carrying it forward is just payload.
Do
- Store attempts in a list, not in a variable you reassign. One record per attempt: the verifier output, the patch the attempt actually wrote, and which tool step errored first.
- Take the patch from the workspace snapshot, before the revert — the real diff, not the model's description of what it changed. The revert is what makes this necessary: once the tree is rolled back, nothing on disk records the wrong path either, so the next attempt has no obstacle to re-deriving the same one.
- Compose the retry prompt from every record, oldest first, each labelled with its attempt number and its verdict, under a heading that says these were already tried and reverted.
- Bound each record. Chimera caps a fed-back diff at 2000 characters and truncates with a marker; an unbounded three-attempt history will dominate the prompt.
- Deduplicate by failure signature. If two attempts failed the same way, keep one and record that it recurred — the repetition is the signal, the second copy is not new information.
- When the signature repeats, stop appending and change something structural: re-plan with the
accumulated causes as planner context (
TaskLedger.context()renders them under "Why earlier attempts failed (do NOT repeat these):"), or escalate to a stronger model. More feedback about the same dead end does not leave the dead end. - Emit a countable event each time you inject history, so a benchmark arm can prove the injection fired at all.
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 · 104 lines · 44 tokens per session scan A 62dcc2aa830e
chimera-carry-the-failure-forward is a skill published in the GitHub repository brcampidelli/chimera-agent (25 stars, last pushed today), licensed Apache-2.0. It adds 44 tokens to every session and 1,271 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.