agentmods.dev

mcp-zoekt: Agent for Claude Code

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

speckit.implement is an agent for Claude Code from jahales/mcp-zoekt. It costs 14 tokens per session (2,019 once invoked), scanned A, a copy of speckit.implement, Apache-2.0.

An implementation agent that follows the tasks written in a project's tasks.md file after a feature plan has been created.

In plain words
What is it for?
Use it to carry out planned feature work in repositories that use the Specify task-and-checklist workflow.
Why use it?
It turns a written plan into a sequence of implementation steps and checks project checklists before proceeding.

Agent for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

This is jahales/mcp-zoekt's own configuration. It tells Claude Code how to work on mcp-zoekt 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 mcp-zoekt configures →

not rated 5repo 1mo ago A scan 14 tokens copy · 88% Apache-2.0
View source ↗ jahales/mcp-zoekt
Reuse

Borrowing it

Nothing to install: this file belongs to jahales/mcp-zoekt. 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/jahales/mcp-zoekt/main/.github/agents/speckit.implement.agent.md
Clone the repo
git clone --depth 1 https://github.com/jahales/mcp-zoekt

Made for: Claude Code.

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/jahales/mcp-zoekt/speckit.implement.svg)](https://agentmods.dev/agents/jahales/mcp-zoekt/speckit.implement)
Your own site
<a href="https://agentmods.dev/agents/jahales/mcp-zoekt/speckit.implement"><img src="https://agentmods.dev/badge/agents/jahales/mcp-zoekt/speckit.implement.svg" alt="Measured on agentmods" 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,019 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 88% 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.02019
Opus 5 $0.00007 $0.01009
Sonnet 5 $0.00003 $0.00404
Haiku 4.5 $0.00001 $0.00202

Measured 7d ago against content hash 02a5d54c313b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-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 7d 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

88% identical to speckit.implement — 67 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 · 136 lines

How it starts

The opening of the file, as written. The whole thing — 136 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).

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:

      | Checklist | Total | Completed | Incomplete | Status |
|-----------|-------|-----------|------------|--------|
| ux.md     | 12    | 12        | 0          | ✓ PASS |
| test.md   | 8     | 5         | 3          | ✗ FAIL |
| security.md | 6   | 6         | 0          | ✓ PASS |

    • Calculate overall status:

      • PASS: All checklists have 0 incomplete items
      • FAIL: One or more checklists have incomplete items

    • If any checklist is incomplete:

      • Display the table with incomplete item counts
      • STOP and ask: "Some checklists are incomplete. Do you want to proceed with implementation anyway? (yes/no)"
      • Wait for user response before continuing
      • If user says "no" or "wait" or "stop", halt execution
      • If user says "yes" or "proceed" or "continue", proceed to step 3

    • If all checklists are complete:

      • Display the table showing all checklists passed
      • Automatically proceed to step 3

  3. Load and analyze the implementation context:

    • REQUIRED: Read tasks.md for the complete task list and execution plan
    • REQUIRED: Read plan.md for tech stack, architecture, and file structure
    • IF EXISTS: Read data-model.md for entities and relationships
    • IF EXISTS: Read contracts/ for API specifications and test requirements
    • IF EXISTS: Read research.md for technical decisions and constraints
    • IF EXISTS: Read quickstart.md for integration scenarios

Read the full file on GitHub · 136 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. 7d ago First seen · 136 lines · 14 tokens per session scan A 02a5d54c313b

Subscribe to this mod's changes

speckit.implement is an agent published in the GitHub repository jahales/mcp-zoekt (5 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 14 tokens to every session and 2,019 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to speckit.implement, differing in 67 lines, and is treated as a copy.

Planningai-toolscode-searchmcpmodel-context-protocolzoekt
Related

Other agents, from other repositories

semble-search

Code search agent for exploring any codebase. Use for finding code by intent, locating implementations, understanding how something works, or discovering related code. Prefer over runshellcommand/readfile for any semantic or exploratory question.

MinishLab/semble · 46 tokens

semble-search

Code search agent for exploring any codebase. Use for finding code by intent, locating implementations, understanding how something works, or discovering related code. Prefer over Bash/Read for any semantic or exploratory question.

MinishLab/semble · 44 tokens

semble-search

Code search agent for exploring any codebase. Use for finding code by intent, locating implementations, understanding how something works, or discovering related code. Prefer over shell/read tools for any semantic or exploratory question.

MinishLab/semble · 44 tokens

security-reviewer

A separate agent that reviews security-sensitive code changes without editing files or reading sensitive configuration. It focuses on authentication, permissions, payments, deletion, and handling of outside input.

ezBuilder/code-brain · 27 tokens

pkm-capture

Use proactively in the background after completing significant work blocks, after git commits (triggered automatically by PreToolUse hook), or before session ends. Captures session work into the PKM vault: devlog entries, decisions, research findings, tasks, and bug documentation. Conservative — most exchanges produce…

AdrianV101/obsidian-pkm-plugin · 476 tokens

vault-explorer

Use proactively when researching what the vault knows about a topic, before creating new notes, or when exploring existing knowledge and connections. Run in foreground — results inform the caller's next steps. Examples: Context: User asks about a topic before creating new content. user: "What does the vault already…

AdrianV101/obsidian-pkm-plugin · 252 tokens