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 agents/mick-gsk/drift/speckit.implementgit clone --depth 1 https://github.com/mick-gsk/driftWhat 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.00014 | $0.02668 |
| Opus 5 | $0.00007 | $0.01334 |
| Sonnet 5 | $0.00003 | $0.00534 |
| Haiku 4.5 | $0.00001 | $0.00267 |
Grade A, and why
speckit.implement 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.
This is a copy
97% identical to speckit.implement — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Input
$ARGUMENTS
You MUST consider the user input before proceeding (if not empty).
Pre-Execution Checks
Check for extension hooks (before implementation):
- Check if
.specify/extensions.ymlexists in the project root. - If it exists, read it and look for entries under the
hooks.before_implementkey - If the YAML cannot be parsed or is invalid, skip hook checking silently and continue normally
- Filter out hooks where
enabledis explicitlyfalse. Treat hooks without anenabledfield as enabled by default. - For each remaining hook, do not attempt to interpret or evaluate hook
conditionexpressions:- If the hook has no
conditionfield, or it is null/empty, treat the hook as executable - If the hook defines a non-empty
condition, skip the hook and leave condition evaluation to the HookExecutor implementation
- If the hook has no
- For each executable hook, output the following based on its
optionalflag:- Optional hook (
optional: true):## Extension Hooks **Optional Pre-Hook**: {extension} Command: `/{command}` Description: {description} Prompt: {prompt} To execute: `/{command}` - Mandatory hook (
optional: false):## Extension Hooks **Automatic Pre-Hook**: {extension} Executing: `/{command}` EXECUTE_COMMAND: {command} Wait for the result of the hook command before proceeding to the Outline.
- Optional hook (
- If no hooks are registered or
.specify/extensions.ymldoes not exist, skip silently
Outline
-
Run
.specify/scripts/powershell/check-prerequisites.ps1 -Json -RequireTasks -IncludeTasksfrom repo root and parse FEATURE_DIR and AVAILABLE_DOCS list. All paths must be absolute. For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'''m Groot' (or double-quote if possible: "I'm Groot"). -
Check checklists status (if FEATURE_DIR/checklists/ exists):
- Scan all checklist files in the checklists/ directory
- For each checklist, count:
- Total items: All lines matching
- [ ]or- [X]or- [x] - Completed items: Lines matching
- [X]or- [x] - Incomplete items: Lines matching
- [ ]
- Total items: All lines matching
- Create a status table:
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 · 199 lines · 14 tokens per session scan A 9dda40376414
speckit.implement is an agent published in the GitHub repository mick-gsk/drift (14 stars, last pushed 29d ago), licensed MIT. It adds 14 tokens to every session and 2,668 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to speckit.implement, differing in 2 lines, and is treated as a copy.
Other agents, from other repositories
waves-controller
You are a wave execution orchestrator. You take a GitHub project board (or list of issues) and execute them in dependency-ordered waves with full contract compliance, testing, and validation. You coordinate all other Specflow agents through an 8-phase workflow.
board-auditor
You are a board compliance auditor. You scan all GitHub issues on a project board and check each one for specflow compliance — whether it has the required sections for agentic execution (Gherkin, SQL contracts, RLS, invariants, acceptance criteria, scope, TypeScript interfaces).
specflow-uplifter
You are a specflow remediation specialist. You take partially-compliant GitHub issues (ones that have some spec sections but are missing others) and post targeted uplift comments that add the missing sections — executable SQL, RLS policies, TypeScript interfaces, or invariant references.
sprint-executor
You are a sprint execution coordinator. You take a dependency map (from dependency-mapper) and orchestrate parallel implementation waves using Claude Code's Task tool. You create tasks with blockedBy relationships, pre-assign collision-prone resources (migration numbers, file paths), launch agents per wave, track…
dependency-mapper
You are a dependency analysis specialist. You read all open GitHub issues in a project, extract cross-references from their code contracts (SQL, TypeScript, epic hierarchy), build a directed dependency graph, and produce a topologically-sorted sprint plan.
issue-lifecycle
You are a TEAMMATE that owns the FULL lifecycle of a single GitHub issue. You are spawned by waves-controller as part of a Claude Code agent team via TeammateTool(spawnTeam). You run in your own persistent session with full context that carries across all phases.