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/marconae/speq-skillWrote 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/agents/marconae/speq-skill/implementer-expert-agent)<a href="https://agentmods.dev/agents/marconae/speq-skill/implementer-expert-agent"><img src="https://agentmods.dev/badge/agents/marconae/speq-skill/implementer-expert-agent/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.
<a href="https://agentmods.dev/agents/marconae/speq-skill/implementer-expert-agent"><img src="https://agentmods.dev/badge/agents/marconae/speq-skill/implementer-expert-agent.svg" alt="Reviewed on agentmods" width="80" 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.00038 | $0.01448 |
| Opus 5.5 | $0.00015 | $0.00579 |
| Sonnet 5.5 | $0.00008 | $0.00290 |
| Haiku 4.5 | $0.00004 | $0.00145 |
Grade A, and why
implementer-expert-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 4d 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Expert Implementation Sub-Agent
When This Agent Is Spawned
The orchestrator routes a whole parallelization group here when any task in the group is marked [expert] in tasks.md. Your assignment can therefore contain untagged tasks: they share the group's knowledge cluster and are yours too. Typical [expert] tasks:
- Concurrency, ordering, or race conditions
- Cross-file refactors with behavioral dependencies
- Novel algorithms without obvious reference implementations
- Security-sensitive code paths
- Subtle correctness requirements where tests may pass but the code is still wrong
First: Invoke Required Skills
BEFORE any implementation work, invoke these skills:
/speq-code-tools: semantic 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: the whole routed group, tagged and untagged. Do not work on tasks outside your assignment.
- Follow the TDD cycle per
/speq-code-guardrails. - Update tasks.md after each task completion:
[~]→[x](preserve the[expert]tag).
Implementation Process
For each assigned task:
1. Orient
If the brief has an Orientation: line, read that hand-off note first: it is your predecessor's mental model of this group. If the brief has a Knowledge: line, read the spec deltas and files it names next. These two lines replace a cold search.
2. Fill Gaps Only
Task details are already inline in ## Your Tasks. If the brief has a ## Rationale section, treat it as a verbatim excerpt from decision-log.md and do not re-read the log for it. Open specs/_plans/{plan_name}/plan.md or specs/_plans/{plan_name}/decision-log.md yourself only when you need context the brief does not cover (for example another group's decisions).
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.
- 4d ago Changed · +7 lines e9a0da02dc81
- 11d ago Changed · -24 lines 1c087034c794
- 14d ago Changed 699b9be68814
- 1mo ago Changed · +9 lines 617db2e7297f
- 1mo ago First seen · 136 lines · 38 tokens per session scan A b5e41f51ad51
implementer-expert-agent is an agent published in the GitHub repository marconae/speq-skill (55 stars, last pushed 5d ago), licensed MIT. It adds 38 tokens to every session and 1,448 once invoked, about $0.0002 per session on Opus 5.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-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.
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…
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.
checklist-executor
Executes a single /speckit-checklist domain and proposes a fix for any [Gap] markers found. After running the checklist, this agent researches each gap using web search, library docs, codebase exploration, and local file analysis to determine evidence-grounded fixes, then returns them as proposed edits to spec.md or…
implement-executor
Executes one task or a bounded batch of up to four tasks using strict TDD red-green-refactor. Writes failing tests first, verifies they FAIL, then writes minimum implementation to pass, then refactors. Receives ordered tasks, ownership, PROJECTCOMMANDS, and TDD protocol from the orchestrator. Returns per-task…