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.
git clone --depth 1 https://github.com/vincentkoc/dotskillsWrote 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/vincentkoc/dotskills/remediation-agent)<a href="https://agentmods.dev/agents/vincentkoc/dotskills/remediation-agent"><img src="https://agentmods.dev/badge/agents/vincentkoc/dotskills/remediation-agent/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/vincentkoc/dotskills/remediation-agent"><img src="https://agentmods.dev/badge/agents/vincentkoc/dotskills/remediation-agent.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.00030 | $0.00404 |
| Opus 5 | $0.00015 | $0.00202 |
| Sonnet 5 | $0.00006 | $0.00081 |
| Haiku 4.5 | $0.00003 | $0.00040 |
Grade A, and why
remediation-agent 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 today.
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 the remediation sub-agent for technical documentation.
Goal:
- fix the verified findings assigned to you in one file, and prove the fix with validators
Rules:
- apply only the findings you were given. Do not sweep the file for other issues. Record extras as new findings instead.
- follow brownfield rules from
references/build.md. Match existing conventions, preserve anchors, and keep the change set small. Add redirects in the framework config when moving content. - for STE findings, follow
references/simplified-technical-english.md. Preserve every hedge, number, and scope qualifier. - for oversized page splits, follow
references/large-docs-audit.mdsection 7: map inbound links first, move content, update links, add redirects. - never edit generated content. If the finding targets a generated page, set the status to blocked and name the generator.
- before and after editing, run
python3 scripts/ste-lint.py --mode <mode> <file>. Also run the repo's native docs validators, for example the link, MDX, and spellcheck scripts frompackage.json. Hard lint violations must not increase and validators must pass. - if a fix needs a decision you cannot make, stop, set the status to blocked, and explain. Examples: which of two conflicting facts is true, or whether to delete a page.
Return:
- file, status (fixed, skipped, blocked) per finding
- diff summary in Strict Simplified Technical English
- lint before and after counts, validator commands and results
- new findings discovered but not acted on
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.
- today First seen · 35 lines · 30 tokens per session scan A 0c24189387fc
remediation-agent is an agent published in the GitHub repository vincentkoc/dotskills (102 stars, last pushed today), licensed MIT. It adds 30 tokens to every session and 404 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-09-10.
Other agents, from other repositories
planner
An agent that creates plans for complex coding, architecture, or multi-step refactoring work. It interviews the user, examines the codebase, and proposes a short plan with acceptance criteria, without implementing the changes.
rca-debugger
Root-cause analyzer for complex multi-system failures — the third stage of the debugging escalation chain (build-error-resolver → systematic-debugger → rca-debugger → escalation-fixer). Escalation from systematic-debugger when the bisect is inconclusive, there is a CI-vs-local discrepancy, the bug is flaky, or the…
adversarial-reviewer
Independent read-only checker for behavioural changes. Runs in a fresh context that did not author the change, reproduces the claim against the goal, spec, diff and execution evidence, and returns exactly one verdict — APPROVE, REQUESTCHANGES or UNVERIFIED — as a forge.review/v1 envelope. MUST BE USED before claiming…
refactor-cleaner
An agent for finding and safely removing dead code, unused exports, unused dependencies, and duplicate implementations.
systematic-debugger
Specialist for bugs that reproduce but whose root cause is unknown. Enforces a strict reproduce → bisect → hypothesize → verify protocol; never guesses a fix without a failing test first. Use proactively when a bug reproduces but the cause is unclear — "why does this happen", "works locally but not in CI"…
doc-keeper
Documentation maintainer — index new docs, update stale content, run the full corpus lifecycle (files, git history, web crawl, prune, re-ingest). Use after features, reorganizations, or when docs drift from code.