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/postindustria-tech/agentic-toolkit/remediatenpx skills add postindustria-tech/agentic-toolkit --skill remediategit clone --depth 1 https://github.com/postindustria-tech/agentic-toolkitWhat 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.00112 | $0.01060 |
| Opus 5 | $0.00056 | $0.00530 |
| Sonnet 5 | $0.00022 | $0.00212 |
| Haiku 4.5 | $0.00011 | $0.00106 |
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 2d 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Entity Test Remediation
Systematically convert test stubs into real tests and fix production code to make them pass. Batch-by-batch, TDD-driven.
Args
/dev-practices-remediate <entity-name-1> [entity-name-2] ...
Entity names (space-separated). Each must already have a test suite. If the suite doesn't exist, the formula STOPS at pre-check.
Hard Gate: Pre-Check
The first atom checks if the entity test suite exists:
STOP: No entity test suite for {entity}.
Create the test surface map with obligations and stubs first.
Remediation requires a surface to remediate against.
This prevents remediation without a surface map -- the whole point of the layered approach.
Batch Sizing
Each molecule handles one batch per entity (recommended 5-15 stubs):
- Too few stubs per batch = too many molecules
- Too many = too much context for one session
Multiple runs against the same entity are expected:
/dev-practices-remediate creative # batch 1: P0 schema compliance stubs
/dev-practices-remediate creative # batch 2: P1 lifecycle stubs
/dev-practices-remediate creative # batch 3: P2 edge case stubs
Protocol
Step 1: Cook the molecule
python3 ${CLAUDE_PLUGIN_ROOT}/skills/dev-practices-execute/scripts/cook_formula.py \
--formula ${CLAUDE_PLUGIN_ROOT}/skills/dev-practices-execute/formulas/entity-remediate.yaml \
--var "ENTITY_NAMES={all_args}" \
--epic-title "Remediate: {all_args}"
Dry run first (recommended):
python3 ${CLAUDE_PLUGIN_ROOT}/skills/dev-practices-execute/scripts/cook_formula.py \
--formula ${CLAUDE_PLUGIN_ROOT}/skills/dev-practices-execute/formulas/entity-remediate.yaml \
--var "ENTITY_NAMES={all_args}" \
--epic-title "Remediate: {all_args}" \
--dry-run
Step 2: Walk the molecule
bd ready -> bd show <atom-id> -> execute -> bd close <atom-id> -> repeat
Each entity goes through: pre-check -> plan-batch -> review -> triage -> implement-red -> fix-green -> verify -> commit.
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.
- 2d ago First seen · 129 lines · 112 tokens per session scan A a3e7d0c0fea6
remediate is a skill published in the GitHub repository postindustria-tech/agentic-toolkit (2 stars, last pushed 1mo ago), licensed MIT. It adds 112 tokens to every session and 1,060 once invoked, about $0.0006 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
agent-integration
Run all three agent integration phases sequentially: research, write-tests, and implement using E2E-first TDD (unit tests written last). For individual phases, use /agent-integration:research, /agent-integration:write-tests, or /agent-integration:implement. Use when the user says "integrate agent", "add agent…
engram-testing-coverage
TDD and coverage standards for Engram. Trigger: When implementing behavior changes in any package.
code-assist
Guides implementation of code tasks using test-driven development in an Explore, Plan, Code, Commit workflow. Acts as a Technical Implementation Partner and TDD Coach — following existing patterns, avoiding over-engineering, and producing idiomatic, modern code.
tdd
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
css-design-tdd
Test-driven CSS design system modifications. Run checks before/after CSS changes to verify token usage, variable definitions, fallbacks, and consistency. Use when modifying CSS tokens, fixing design inconsistencies, or auditing CSS architecture.
mobiai-mobile-tdd
You MUST use this before writing any implementation code for a mobile feature, bug fix, refactor, or behavior change. Tests come before implementation — no exceptions.