Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/VoxTechnologies/transmute-frameworknpx agentmods add skills/voxtechnologies/transmute-framework/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/voxtechnologies/transmute-framework/remediate)<a href="https://agentmods.dev/skills/voxtechnologies/transmute-framework/remediate"><img src="https://agentmods.dev/badge/skills/voxtechnologies/transmute-framework/remediate/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/voxtechnologies/transmute-framework/remediate"><img src="https://agentmods.dev/badge/skills/voxtechnologies/transmute-framework/remediate.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.00101 | $0.03432 |
| Opus 5.5 | $0.00040 | $0.01373 |
| Sonnet 5.5 | $0.00020 | $0.00686 |
| Haiku 4.5 | $0.00010 | $0.00343 |
Grade A, and why
remediate 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 19d 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 — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stage 6R: Runtime Remediation
Read the Stage 6V verification report, categorize every failure by fixability, auto-fix all mechanical issues, and produce a human-review TODO list for issues requiring judgment — then re-verify to confirm fixes work. Lead a multi-agent runtime remediation project (teammates are Agent-tool subagents; see the pipeline agent's Execution Model).
Read the detailed guide at ${CLAUDE_SKILL_DIR}/references/remediate-detailed-guide.md for full fixability taxonomy, teammate prompts, safety rules, and report templates.
Prerequisites
-
Stage 6V must have produced a report:
./plancasting/_audits/visual-verification/report.mdmust exist. If not, run Stage 6V first. -
Feature Scenario Matrix must exist: Verify
./plancasting/_audits/visual-verification/feature-scenario-matrix.mdexists (generated by Stage 6V). -
6V gate decision check:
- 6V PASS: Skip 6R entirely -- proceed to 6P or 6P-R. No failures to remediate.
- 6V CONDITIONAL PASS with 6V-A/6V-B issues: Proceed with 6R.
- 6V CONDITIONAL PASS with ONLY 6V-C issues: Skip 6R -- proceed to 6P or 6P-R. 6R cannot fix 6V-C.
- 6V FAIL: STOP -- fix critical issues manually first, then re-run 6V.
-
Create output directory:
mkdir -p ./plancasting/_audits/runtime-remediation
Input
- 6V Verification Report:
./plancasting/_audits/visual-verification/report.md(primary input) - Feature Scenario Matrix:
./plancasting/_audits/visual-verification/feature-scenario-matrix.md - Codebase: Backend and frontend directories
- Tech Stack:
./plancasting/tech-stack.md - Project Rules:
./CLAUDE.md - PRD:
./plancasting/prd/(for understanding intended behavior) - E2E Constants:
./e2e/constants.ts
Check ./plancasting/tech-stack.md for the Session Language setting. Generate all reports in that language. Code and file names remain in English.
Stack Adaptation
Adapt to your plancasting/tech-stack.md: middleware path, route whitelist mechanism, loading state pattern, i18n files, data fetching patterns, backend directory. Replace npm run with your project's package manager per CLAUDE.md.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 19d ago Changed · +2 lines 21d13136f0ec
- 1mo ago First seen · 208 lines · 101 tokens per session scan A 32a4363fb961
remediate is a skill published in the GitHub repository VoxTechnologies/transmute-framework (5 stars, last pushed 8d ago), licensed MIT. It adds 101 tokens to every session and 3,432 once invoked, about $0.0004 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
wp-audit-run
The step detail of the /wp-audit run, split out of commands/wp-audit.md so the command stays a short map — site type and local clone, manifest reconciliation, page scope, the agent dispatch prompt, the browser suite, measured findings and verified fixes, the finding ledger, the status vocabulary, the dated…
playwright-debugging
Use when Playwright scripts fail, tests are flaky, selectors stop working, or timeouts occur - provides systematic debugging approach for browser automation issues.
safari-mcp-workflow
Inspect a scoped live site in Safari through Safari Technology Preview's local MCP server. Use for Safari-specific DOM, console, network, screenshot, accessibility, performance, interaction, responsive, or print-media evidence.
reproduce-bug
This skill should be used when reproducing and investigating a bug using logs, console inspection, and browser screenshots. It systematically investigates GitHub issues through log analysis, code inspection, and visual reproduction with Playwright.
soleur-reproduce-bug
This skill should be used when reproducing and investigating a bug using logs, console inspection, and browser screenshots. It systematically investigates GitHub issues through log analysis, code inspection, and visual reproduction with Playwright.
site-audit
This skill should be used when the user invokes /site-audit with a URL. It crawls the target website and produces a quality audit report covering broken links, spelling errors, console errors, and visual issues.