Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add raisedadead/claude-code-plugins/plugin install dossierWrote 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/raisedadead/claude-code-plugins/backprop)<a href="https://agentmods.dev/skills/raisedadead/claude-code-plugins/backprop"><img src="https://agentmods.dev/badge/skills/raisedadead/claude-code-plugins/backprop/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/raisedadead/claude-code-plugins/backprop"><img src="https://agentmods.dev/badge/skills/raisedadead/claude-code-plugins/backprop.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.00071 | $0.02936 |
| Opus 5.5 | $0.00028 | $0.01174 |
| Sonnet 5.5 | $0.00014 | $0.00587 |
| Haiku 4.5 | $0.00007 | $0.00294 |
Grade A, and why
backprop 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 2d 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 — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ds:backprop — bug → invariant protocol
Six steps. Append-only on §B + §V. Resumable.
Inputs
<B-id>(e.g.B5): existing bug row, resume / amend.<bug-description>free text: new bug, scaffold a §B row from it.--resume: explicit override of the auto-detected resume point.
Steps
0. Helpers
DOSSIER.md writes go through the bundled helpers (${CLAUDE_PLUGIN_ROOT}/FORMAT.md §15): "${CLAUDE_PLUGIN_ROOT}"/cli/ds row-flip <dir> <id> <state> [cite] flips a §T state cell, "${CLAUDE_PLUGIN_ROOT}"/cli/ds s-append <dir> "<event>" appends §S. The §S code-fences below show the full line — pass only the text after the timestamp, which the script prepends.
There is no row-flip for §B. ds row-flip <dir> B<N> <state> exits 1 printing ds row-flip: refuses Bugs rows (no state column — would destroy cells); use ds:backprop — §B carries id | bug | root cause | invariant added | fix cite and no state column at all (FORMAT.md §9, §15). Every §B mutation in this skill is therefore an atomic whole-file write: the row append in step 6, the invariant added update in step 7, the fix cite update in step 8.
1. Locate live dossier
Per ds:status step 1. Refuse when there is none.
2. Acquire lock
Write <dir>/.ds-lock with skill: "ds:backprop", target: "B<N-or-pending>".
3. Resume detection
Read §S, grep ds:backprop <target>:
| Last event | Resume point |
|---|---|
| (none) | full run from step 4 |
START |
step 4 (re-scope) |
flake=<rate> |
1.0 → step 5; 0.0 → step 4 (re-scope); 0<r<1 → write closed §B row (step 4.5 flaky branch) then step 9 |
test=<sha> |
step 6 |
§B=B<N> |
step 7 (invariant decision) |
§V=V<N> |
step 8 (fix) |
fix=<sha> |
step 9 (close) |
DONE |
exit |
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.
- 2d ago Changed · +2 lines 786de219c32e
- 14d ago Changed 4e31bc2ddb11
- 18d ago Changed · -3 lines c3de1b2bba76
- 1mo ago First seen · 224 lines · 71 tokens per session scan A 7956f8c6b932
backprop is a skill published in the GitHub repository raisedadead/claude-code-plugins (3 stars, last pushed today), licensed ISC. It adds 71 tokens to every session and 2,936 once invoked, about $0.0003 per session on Opus 5.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
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
deck-retro
Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…