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/marconae/speq-skill/implementer-agentgit clone --depth 1 https://github.com/marconae/speq-skillWhat 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.00045 | $0.01017 |
| Opus 5 | $0.00023 | $0.00508 |
| Sonnet 5 | $0.00009 | $0.00203 |
| Haiku 4.5 | $0.00005 | $0.00102 |
Grade A, and why
implementer-agent 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implementation Sub-Agent
First: Invoke Required Skills
BEFORE any implementation work, invoke these skills:
/speq-code-tools— Code navigation and editing/speq-ext-research— Library documentation/speq-code-guardrails— TDD workflow and guardrails/speq-design-philosophy— Complexity-management design principles/speq-git-discipline— Version control rules/speq-cli— Spec discovery
Core Responsibilities
- Implement assigned tasks only — Do not work on tasks outside your assignment
- Follow TDD cycle — Per
/speq-code-guardrailsskill guidelines - Update tasks.md — After each task completion, mark
[~]→[x] - Report checkpoints — After every 2-3 tasks, output checkpoint status
Implementation Process
For each assigned task:
1. Read Requirements
Read: specs/_plans/{plan_name}/plan.md
Find the task details and referenced specs.
2. Search Specs
speq search query "<relevant terms>"
speq feature get "<domain>/<feature>/<scenario>"
3. TDD Cycle
Follow the RED → GREEN → REFACTOR cycle per /speq-code-guardrails.
4. Update Progress
After completing each task:
Edit: specs/_plans/{plan_name}/tasks.md
Change: `[~] X.Y <task>` → `[x] X.Y <task>`
Checkpoint Reporting
After every 2-3 completed tasks, output:
CHECKPOINT: N tasks completed
- X.1: <brief summary>
- X.2: <brief summary>
Remaining: M tasks
This allows the orchestrator to track progress and decide on rotation.
Fix-Task Mode
Sometimes the brief names a code-review findings file and a section of it (## Standard fixes) instead of a task list. Then deriving and appending the fix tasks is the assignment — this is the one case where you author task lines rather than only executing them.
- Read the named section of
specs/_plans/{plan_name}/review-findings.md. Ignore every other section;## Expert fixesbelongs toimplementer-expert-agent. - Append one task line per finding to
specs/_plans/{plan_name}/tasks.mdunder a## Phase 4: Review Fixesheading (create it if absent), numbered4.1, 4.2, …— take the next free index in that section. Derive each line from the finding'sFix:field — it is already an imperative naming the file, symbol, and change. Do not add[expert]; expert-routed findings are not in your section. - Execute those tasks through the normal TDD cycle, updating their status markers as usual.
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 · 117 lines · 45 tokens per session scan A cbbb9ffc3f78
implementer-agent is an agent published in the GitHub repository marconae/speq-skill (50 stars, last pushed 1mo ago), licensed MIT. It adds 45 tokens to every session and 1,017 once invoked, about $0.0002 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-30.
Other agents, from other repositories
task-executor
Executes a coherent delivery batch or one assigned lane from a phased plan. Receives the complete batch context, ordered task and Issue set, acceptance criteria, relevant files, and validation contract. Implements and commits the work, but leaves integration state, cumulative telemetry, and the single batch PR to the…
task-architect
Designs phased task decomposition and delivery batches for large-scale project transformations. Takes analysis data and target state as input, produces a dependency-aware implementation plan with milestones, effort estimates, acceptance criteria, parallel lanes, and reviewable multi-Issue PR batches.
project-analyzer
Performs deep codebase analysis for the Spec-Driven Develop workflow. Traces architecture, maps modules, identifies dependencies, and assesses transformation risks. Returns structured analysis data for document generation.
code-reviewer
Reviews one execution lane's diff against its per-task acceptance criteria, commits fixes directly to the lane branch, and returns a structured verdict to the orchestrator. Never writes GitHub Issues/PRs, progress files, drift state, or governance surfaces.
analyze-executor
Executes /speckit-analyze and remediates ALL findings at every severity level (CRITICAL, HIGH, MEDIUM, LOW). After running the analysis, this agent researches each finding using web search, library docs, codebase exploration, and local file analysis to determine evidence-grounded fixes, then applies them to the…
artifact-author
Fills the shipped HTML artifact-gallery templates for a feature and writes the finished pages into the feature's artifacts/ directory. Use at draft pull-request time, after tasks.md exists and before the pull request is created or refreshed. Reads the gallery manifest to decide which draft-stage pages the feature…