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 agentmods add instructions/fvckprth/remediate/claude-mdgit clone --depth 1 https://github.com/fvckprth/remediateWrote 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/instructions/fvckprth/remediate/claude-md)<a href="https://agentmods.dev/instructions/fvckprth/remediate/claude-md"><img src="https://agentmods.dev/badge/instructions/fvckprth/remediate/claude-md.svg" alt="Measured on agentmods" 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 | $0.01842 | $0.01842 |
| Opus 5 | $0.00921 | $0.00921 |
| Sonnet 5 | $0.00368 | $0.00368 |
| Haiku 4.5 | $0.00184 | $0.00184 |
Grade A, and why
remediate CLAUDE.md 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 3d 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 — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Remediate — Claude Code Instructions
Linear ticket format
When creating Linear tickets for this project, follow this spec exactly. Both Parth and his collaborator use this format.
How tickets are created
- Claude creates tickets directly via the Linear MCP (
claude mcp add --transport sse linear https://mcp.linear.app/sse) - Screenshots are captured via Chrome DevTools MCP, saved locally, and the local path is noted in the ticket body for manual drag-drop into Linear
Fields (always set)
| Field | Rule |
|---|---|
| Title | lowercase, human-readable, area prefix required |
| Label | exactly one of Bug, Feature, Improvement (case matches Linear workspace) |
| Status | Backlog |
| Priority | always assigned (see rubric) |
| Project | match an existing Linear project if relevant, otherwise leave blank |
| Assignee | decided per-ticket (do not auto-assign) |
Title prefixes
Pick one based on the primary area changed. Multi-area tickets use the primary area's prefix. If nothing fits, use misc:.
widget:— embedded feedback widget (toolbar, panels, capture flow)capture:— screenshot, video, audio, area selectorannotate:— annotation markers, popovers, highlightingnotes:— voice panel, text note panelreview:— review panel / submission flowserver:— server-side parsing, API routesintegrations:— linear, slack, github, email, webhookinfra:— build, deploy, env, tsup configrepo:— cross-cutting cleanup, tooling, CIskill:— agent skill (SKILL.md)misc:— nothing else fits
Examples:
widget: voice notes don't save offlineintegrations: linear ticket missing prioritycapture: video recording freezes on safari
Priority rubric
- Urgent — blocks the Linear project/milestone the ticket lives in
- High — needed soon after launch, or a significant bug affecting most users
- Normal — real improvement or bug, but launch ships fine without it (Linear calls this "Normal", priority value 3)
- Low — nice-to-have, nitpick, backlog-forever candidate
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.
- 3d ago First seen · 190 lines · 1,842 tokens per session scan A b4ed88a561a1
remediate CLAUDE.md is an instructions file published in the GitHub repository fvckprth/remediate (11 stars, last pushed 3mo ago), licensed MIT. It adds 1,842 tokens to every session, about $0.0092 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 instructions, from other repositories
ESAA-Core AGENTS.md
Instructions for elzobrito/ESAA-Core, covering agents.md — contrato operacional codex/esaa, 1. autoridade e termos, 2. cli e runner, ou configure o runner uma vez por sessão and 3. concorrência.
Kanvas AGENTS.md
Instructions for XMihura/Kanvas, covering canvas workflow — agent instructions, critical rule, session protocol, 1. start of session — read the board and 2. pick a task.
delivery-loop CLAUDE.md
Instructions for blakemartz/delivery-loop, covering claude.md, what this is, the cardinal rule: everything must stay repo-agnostic, layout and config: the one seam.
taskcenter AGENTS.md
AGENTS.md instructions for xiaogezi/taskcenter, covering taskcenter agent rules, safety boundaries, required workflow and verification.
idd-skill idd-resume.instructions.md
Instructions for kurone-kito/idd-skill, covering idd — resume phase, required inputs, step 0 — route classifier, operator-present release and step 1 — identify claim state.
codecrucible AGENTS.md
Instructions for block/codecrucible, covering agent instructions, quick reference and landing the plane (session completion).