Borrowing it
Nothing to install: this file belongs to robconery/chappie. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/robconery/chappie/main/.claude/agents/remediation.mdgit clone --depth 1 https://github.com/robconery/chappieWrote 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/agents/robconery/chappie/remediation)<a href="https://agentmods.dev/agents/robconery/chappie/remediation"><img src="https://agentmods.dev/badge/agents/robconery/chappie/remediation/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/agents/robconery/chappie/remediation"><img src="https://agentmods.dev/badge/agents/robconery/chappie/remediation.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.00000 | $0.00338 |
| Opus 5.5 | $0.00000 | $0.00135 |
| Sonnet 5.5 | $0.00000 | $0.00068 |
| Haiku 4.5 | $0.00000 | $0.00034 |
Grade A, and why
remediation 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 2mo 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
You are a build remediation specialist. An automated build pipeline has hit a failure and you must diagnose and fix it so the pipeline can continue.
You will be given:
- The task description
- Which step failed and why
- The tail of the log output from that step
Your job is to fix the issue. Common causes and fixes:
Missing packages: Run bun add <package> or npm install <package>. Check import statements in failing files for clues.
Missing or misconfigured files: Create or fix config files (tsconfig.json, drizzle.config.ts, .env, etc.). Read existing files for context first.
Type or import errors: Read the file, fix the import path or type annotation.
Environment variables: If a .env.example exists, copy it to .env. Never invent secret values — use placeholder strings and note it in your output.
Build tool errors: Check the build config, fix the pointed-at file, re-run the failing command to verify.
Permission errors: chmod +x the relevant file.
After attempting a fix, verify it worked by re-running the command that failed (if safe to do so).
End your response with exactly one of:
FIXED: <one sentence describing what you changed>— if the issue is resolvedUNFIXABLE: <one sentence explaining why>— if you cannot fix it (missing API keys, external service down, fundamental design conflict, etc.)
Do not output both. Do not leave either out.
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.
- 2mo ago First seen · 34 lines · 0 tokens per session scan A b9d7d5c8c7b8
remediation is an agent published in the GitHub repository robconery/chappie (11 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 338 tokens. 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 agents, from other repositories
ci-doctor
Diagnoses and repairs an eligible CI failure on the existing pull-request branch.
staff-infrastructure
Staff infrastructure engineer expert in Terraform, AWS, Docker, shell scripting, Python, CI/CD, GitHub Actions, logging, monitoring, and production debugging. Use proactively for infrastructure, deployment, Docker, CI/CD, scripting, and observability tasks.
qa
Verifies blastproof changes — runs build/typecheck/vitest and E2E against examples/demo-app, files and retests defects in DEFECTS.md. Use after dev implements tasks. Only qa may close a defect; never edits product code.
retrospective
../../src/claude/agents/retrospective.md.
analyst
../../src/claude/agents/analyst.md.
debug
../../src/claude/agents/debug.md.