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 skills add jstoup111/ai-conductor --skill remediategit clone --depth 1 https://github.com/jstoup111/ai-conductorWrote 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/jstoup111/ai-conductor/remediate)<a href="https://agentmods.dev/skills/jstoup111/ai-conductor/remediate"><img src="https://agentmods.dev/badge/skills/jstoup111/ai-conductor/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/jstoup111/ai-conductor/remediate"><img src="https://agentmods.dev/badge/skills/jstoup111/ai-conductor/remediate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00057 | $0.06587 |
| Opus 5 | $0.00028 | $0.03293 |
| Sonnet 5 | $0.00011 | $0.01317 |
| Haiku 4.5 | $0.00006 | $0.00659 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 383 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Turns a blocking gate into action. When build_review fails, or when prd-audit,
architecture-review --as-built, or the finish verification reports SHIP gaps the daemon would
otherwise HALT on, this skill reasons over each blocking gap and decides how the daemon should
proceed — autonomously where it can, human-in-the-loop only where it must.
Correctness gate: a gap's disposition and its routing target rest on a claim about the gap's
nature. Per the /verify-claims protocol, ground that classification in the audit evidence with a
confidence %, and do not auto-route on an unverified assumption about what the gap is — when the
nature is genuinely uncertain (not just the fix), that low confidence is itself a signal to HALT
for a human rather than to guess a route.
The daemon should be autonomous. So the default is to remediate: translate each gap into concrete, file-scoped work and route it back to the right SDLC step. A HALT is reserved for the two cases a machine genuinely cannot close:
- architectural-clarity — an architectural gap that needs a human decision (ambiguous trade-off, missing ADR, conflicting constraints), not just a code change.
- product-scope — functionality the initial design never accounted for (a real product gap), which needs a human DECIDE amendment.
If a gap can be turned into concrete work, it is not a HALT. This skill plans only — it assigns dispositions and writes tasks. It does not edit code, write tests, or amend the PRD; the step it kicks back to does that.
Run when build_review fails, or at SHIP when a prior audit BLOCKED — dispatched by the
conductor on the blocking path.
Engine-selected build_review case-v1 mode
Use this branch only when this engine context is the engine-stamped build_review case-v1
context declaring domain: "build_review" and mode: "case-v1". It is one judgement by the
existing remediate skill, not a new skill or a second dispatch. Do not create a skill or dispatch
another agent. For every other context, including all SHIP and stall remediation, skip this section
and follow the legacy gap-plan instructions below unchanged.
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.
- today Changed · +2 lines 06ad33e8dd2f
- yesterday Changed · +74 lines 66a828579559
- 4d ago Changed · +9 lines e5ad4837926b
- 9d ago First seen · 298 lines · 57 tokens per session scan A 9e802a2a3afc
remediate is a skill published in the GitHub repository jstoup111/ai-conductor (7 stars, last pushed today), licensed Apache-2.0. It adds 57 tokens to every session and 6,587 once invoked, about $0.0003 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-31.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.