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/benizzio/spec-kit-coding-standards-drift-controlWrote 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/commands/benizzio/spec-kit-coding-standards-drift-control/speckit.coding-standards-drift-control.remediation-plan)<a href="https://agentmods.dev/commands/benizzio/spec-kit-coding-standards-drift-control/speckit.coding-standards-drift-control.remediation-plan"><img src="https://agentmods.dev/badge/commands/benizzio/spec-kit-coding-standards-drift-control/speckit.coding-standards-drift-control.remediation-plan.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.1 | $0.00012 | $0.01734 |
| Opus 5 | $0.00006 | $0.00867 |
| Sonnet 5 | $0.00002 | $0.00347 |
| Haiku 4.5 | $0.00001 | $0.00173 |
Grade A, and why
speckit.coding-standards-drift-control.remediation-plan 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 8d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate Coding Standards Drift Remediation Plan
Append a drift remediation phase to the active feature tasks.md from the current coding-standards drift report.
User Input
$ARGUMENTS
You MUST consider the user input before proceeding (if not empty). The user may ask to focus on specific drift IDs or narrow task generation to a subset of severities.
Purpose
- Add actionable remediation tasks to the active feature's
tasks.mdso/speckit.implementcan execute them. - Run only after the normal implementation task list is complete.
- Keep generated tasks tied to their source pending
CODE-STAND-DRIFT-###report topics for context. - Plan remediation only for findings whose report
StatusisPending. - Reason through each selected pending finding against the report evidence and loaded coding-standards baseline before generating tasks.
- Add or update a concise
**Remediation plan**:section in each selected pending report finding, describing the surgical solution that should fix the drift without changing production or test behavior unnecessarily. - Add the final task that updates successfully remediated report findings to
Status: Resolved; this generated task is the only workflow point that may set findings toResolved. - Do not create
coding-standards-drift-remediation.mdor any other separate remediation checklist.
Prerequisites
- Verify a Spec Kit project exists by checking for
.specify/. - Run
.specify/scripts/bash/check-prerequisites.sh --json --require-tasks --include-tasksfrom repo root and parse the absoluteFEATURE_DIR. - Verify
FEATURE_DIR/coding-standards-drift-report.mdandFEATURE_DIR/tasks.mdexist. If the report is missing, stop and instruct the user to run/speckit.coding-standards-drift-control.reportfirst. - Load the current Spec Kit task format references before editing
tasks.md:.specify/templates/tasks-template.mdwhen present- the existing
FEATURE_DIR/tasks.md
- Using the task state syntax from the current local Spec Kit installation and the existing task file, verify there are no open, unchecked, pending, or reopened tasks in
FEATURE_DIR/tasks.md. If any are present, stop without editingcoding-standards-drift-report.mdortasks.mdand instruct the user to finish implementation with/speckit.implementbefore planning drift remediation.
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.
- 8d ago First seen · 76 lines · 12 tokens per session scan A 1223e7b2c8ca
speckit.coding-standards-drift-control.remediation-plan is a command published in the GitHub repository benizzio/spec-kit-coding-standards-drift-control (2 stars, last pushed 2mo ago), licensed MIT. It adds 12 tokens to every session and 1,734 once invoked, about $0.0001 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 commands, from other repositories
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.