drift: Agent for Claude Code

.github/agents/speckit.implement.agent.md

speckit.implement is an agent for Claude Code from mick-gsk/drift. It costs 14 tokens per session (2,668 once invoked), scanned A, a copy of speckit.implement, MIT.

An implementation command that carries out every task listed in a project’s tasks.md plan, after checking configured pre-implementation hooks.

In plain words
What is it for?
Use it after preparing tasks.md to process the planned implementation, including any applicable extension hooks.
Why use it?
It turns an existing written task plan into an execution step and accounts for project-specific checks that must happen first.

Agent for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

This is mick-gsk/drift's own configuration. It tells Claude Code how to work on drift itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything drift configures →

Part of the drift plugin — 31 skills, 17 agents shipped together

Reuse

Borrowing it

Nothing to install: this file belongs to mick-gsk/drift. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/mick-gsk/drift/main/.github/agents/speckit.implement.agent.md
Clone the repo
git clone --depth 1 https://github.com/mick-gsk/drift

Made for: Claude Code.

Or install drift, the plugin that ships this one along with the rest of its 31 skills, 17 agents.

Wrote 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.

agentmods badge for speckit.implement

README.md
[![agentmods](https://agentmods.dev/badge/agents/mick-gsk/drift/speckit.implement/github.svg)](https://agentmods.dev/agents/mick-gsk/drift/speckit.implement)
Your own site
<a href="https://agentmods.dev/agents/mick-gsk/drift/speckit.implement"><img src="https://agentmods.dev/badge/agents/mick-gsk/drift/speckit.implement/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.

agentmods 80×15 button for speckit.implement

Your own site · 80×15
<a href="https://agentmods.dev/agents/mick-gsk/drift/speckit.implement"><img src="https://agentmods.dev/badge/agents/mick-gsk/drift/speckit.implement.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,668 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 97% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00014 $0.02668
Opus 5.5 $0.00006 $0.01067
Sonnet 5.5 $0.00003 $0.00534
Haiku 4.5 $0.00001 $0.00267

Measured 1mo ago against content hash 9dda40376414, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 1mo 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.

Origin

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.

.github/agents/speckit.implement.agent.md · 199 lines

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.yml exists in the project root.
  • If it exists, read it and look for entries under the hooks.before_implement key
  • If the YAML cannot be parsed or is invalid, skip hook checking silently and continue normally
  • Filter out hooks where enabled is explicitly false. Treat hooks without an enabled field as enabled by default.
  • For each remaining hook, do not attempt to interpret or evaluate hook condition expressions:
    • If the hook has no condition field, 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
  • For each executable hook, output the following based on its optional flag:
    • 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.
      
  • If no hooks are registered or .specify/extensions.yml does not exist, skip silently

Outline

  1. Run .specify/scripts/powershell/check-prerequisites.ps1 -Json -RequireTasks -IncludeTasks from 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").

  2. 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 - [ ]
    • Create a status table:

Read the full file on GitHub · 199 lines

Changes

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.

  1. 1mo ago First seen · 199 lines · 14 tokens per session scan A 9dda40376414

Subscribe to this mod's changes

speckit.implement is an agent published in the GitHub repository mick-gsk/drift (16 stars, last pushed 2mo ago), licensed MIT. It adds 14 tokens to every session and 2,668 once invoked, about $0.0001 per session on Opus 5.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.

Related

Other agents, from other repositories

taniwha-composition

Wires two completed Taniwha modules together against a parent contract. Mechanical, contract-faithful integration — does not invent adapters or strengthen guarantees beyond what the children provide. Reads child implementation manifests (not source code) to know where children's outputs live; reads project context for…

taniwhaai/arai · 118 tokens

taniwha-leaf-implementation

Implements a single Taniwha module against its contract manifest. Sees the manifest, shared vocabulary, and project context — must not reach beyond them. Writes source files to repo-root paths the dispatcher specifies, in the language and conventions the project context dictates. Invoked by the Taniwha dispatcher.…

taniwhaai/arai · 94 tokens

taniwha-verifier

Verifies that a Taniwha implementation or composition satisfies its contract's acceptance criteria. Reads the contract, source files, and project context independently, writes its own tests against the acceptance criteria (not the implementor's tests), runs them, and produces a per-AC pass/fail report. Invoked by the…

taniwhaai/arai · 110 tokens

taniwha-contract-derivation

Derives per-module contracts (manifests) and shared vocabulary from a Taniwha design document. Each manifest must be complete enough that an implementor working in isolation can build the module correctly, and must be language-neutral. Invoked by the Taniwha dispatcher. Returns manifests, shared vocabulary, or a…

taniwhaai/arai · 83 tokens

taniwha-design-doc

Produces the structural design document for a Taniwha project before any code is written. Invoked by the Taniwha dispatcher with the project brief. Returns either a draft design doc (Markdown) or a re-raise. Do not invoke directly — this is part of the Taniwha orchestration flow.

taniwhaai/arai · 72 tokens

taniwha-orchestrator

Ephemeral orchestrator subagent for a Taniwha project. Reads project state from .taniwha/, decides the single next action, writes nextaction.yaml, and exits. Invoked by the dispatcher whenever a build decision is needed. Do not invoke directly from a normal conversation — this agent is part of the Taniwha…

taniwhaai/arai · 81 tokens