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 skills/fvckprth/remediate/remediatenpx skills add fvckprth/remediate --skill remediategit 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/skills/fvckprth/remediate/remediate)<a href="https://agentmods.dev/skills/fvckprth/remediate/remediate"><img src="https://agentmods.dev/badge/skills/fvckprth/remediate/remediate.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.00047 | $0.11210 |
| Opus 5 | $0.00023 | $0.05605 |
| Sonnet 5 | $0.00009 | $0.02242 |
| Haiku 4.5 | $0.00005 | $0.01121 |
Grade A, and why
remediate scanned grade A with 1 finding 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
const res = await fetch(uploadUrl, { How it starts
The opening of the file, as written. The whole thing — 1,117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
tool index
use this section to decide which tool to run. if the user's intent is ambiguous, ask.
| tool | trigger | section |
|---|---|---|
| setup | first-time install of remediate in a project | remediate setup |
| add integration | add or replace a backend integration in an existing setup | add integration |
| wire auth | add user identity (clerk/nextauth/supabase) to the widget | wire auth |
| test endpoint | send a synthetic submission to verify the route works | test endpoint |
| upgrade | check for updates and upgrade to latest version | upgrade |
| scaffold dashboard | create an admin page to view submitted feedback | scaffold feedback dashboard |
| capture gating | configure which capture modes are available | add capture type gating |
| remove | clean uninstall of remediate from the project | remove remediate |
if remediate is not yet in package.json, always run setup first. if it is already installed, route to the matching tool above.
Remediate Setup
set up the remediate feedback widget in this project. one component on the client, one route on the server. the route content depends on which backend the project already uses.
steps
-
detect package manager
- check for
pnpm-lock.yaml,yarn.lock,bun.lockb, orpackage-lock.json - use the matching package manager for install commands
- default to npm if none found
- check for
-
check if already installed
- look for
remediateinpackage.jsondependencies - if not found, install it:
pnpm add remediate(or the matchingnpm/yarn/buncommand) - if found, skip install and continue
- look for
-
check if already configured
- search for
<Remediate,import { Remediate }, orfrom "remediate"insrc/orapp/ - if found, report that remediate is already set up and exit (don't double-mount)
- search for
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.
- 4d ago First seen · 1,117 lines · 47 tokens per session scan A 532760d4b3ed
remediate is a skill published in the GitHub repository fvckprth/remediate (11 stars, last pushed 3mo ago), licensed MIT. It adds 47 tokens to every session and 11,210 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
migrate-radix-to-base
Migrates React projects and components from Radix UI to Base UI. Use when asked to migrate from radix, move to base-ui, convert radix primitives, or switch a shadcn project's base library. Handles single components ("migrate accordion") and whole projects.
copilotkit-upgrade
Use when migrating a CopilotKit v1 application to v2 -- updating package imports, replacing deprecated hooks and components, switching from GraphQL runtime to AG-UI protocol runtime, and resolving breaking API changes.
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
material-ui-tailwind
Integrates Material UI with Tailwind CSS v4 using cascade layers (enableCssLayer, @layer order) and documents Tailwind v3 interoperability (preflight, important, injectFirst, portals). Use when combining MUI with Tailwind utilities, slotProps className, or theme token bridges.
flags
Use when you need to check feature flag states, compare channels, or debug why a feature behaves differently across release channels.
verify
Use when you want to validate changes before committing, or when you need to check all React contribution requirements.