What is implement-spec?

A workflow for implementing a complete specification whose tickets form a task graph, meaning some tickets must wait for others before they can start. It coordinates exploration, implementation, and the final branch of work.

Use it to implement a full spec across multiple tickets, delegate independent work, and track the files and notes that provide shared context.

It helps manage dependencies and parallel work in a large specification without treating tickets as an unstructured checklist.

How 51ck/frontier-mcp configures Claude Code and Codex

Reuse

Borrowing it

Nothing to install: this file belongs to 51ck/frontier-mcp. 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/51ck/frontier-mcp/master/.agents/skills/implement-spec/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/51ck/frontier-mcp

Made for: Claude Code, Codex.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/51ck/frontier-mcp/implement-spec/github.svg)](https://agentmods.dev/skills/51ck/frontier-mcp/implement-spec)

Your own site

<a href="https://agentmods.dev/skills/51ck/frontier-mcp/implement-spec"><img src="https://agentmods.dev/badge/skills/51ck/frontier-mcp/implement-spec/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/51ck/frontier-mcp/implement-spec"><img src="https://agentmods.dev/badge/skills/51ck/frontier-mcp/implement-spec.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 9 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 437 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 100% 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.

Model	Per session	Once invoked
Fable 5.1	$0.00009	$0.00437
Opus 5.5	$0.00004	$0.00175
Sonnet 5.5	$0.00002	$0.00087
Haiku 4.5	$0.00001	$0.00044

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

Security

Grade A, and why

implement-spec 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

100% identical to implement-spec — 25 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.

.agents/skills/implement-spec/SKILL.md · 36 lines

What it actually says

You have been provided a spec. This spec should have tickets associated with it, describing how to implement the spec.

The goal is a PR which implements the entire spec on a single branch.

The tickets are not a list of steps. They are a task graph with blocking relationships between them. This means there is always a frontier of tickets which are ready to be grabbed.

Communication to and from subagents should be sparse. Communicate primarily through context pointers: to the spec, tickets, research notes, and previous commits. Don't duplicate information already available via pointers.

Implementer subagents should be run in the background where possible for maximum concurrency.

Steps

Read the spec and tickets. Read enough to understand the task graph.
(optional) Use an exploration subagent to conduct any exploration required by the tickets - relevant codebase files or external documentation. Ensure the exploration subagent can save files - it should save its markdown notes in a directory outside the repo, accessible by all future subagents. This lets implementer subagents focus on implementation rather than exploration.
Create a branch, and a draft PR. The PR should be marked as 'closing' the spec issue and tickets.
Use implementer subagents to implement each ticket. Each implementer subagent should work in its own worktree, on its own branch.
Once an implementer subagent completes, merge its work to the PR branch with a merger subagent.
If this changes the frontier of available tickets, kick off more implementer subagents to work on the new tickets. This allows for maximum concurrency.
Once all tickets are complete, run /code-review on the PR branch. Fix all issues raised by the code review in a single implementer subagent.
Mark the PR as ready for review.
Clean up all implementer subagent worktrees.

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

agents/openai.yaml 143 B

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.

1mo ago First seen · 36 lines · 9 tokens per session scan A f703b5f41df9

Subscribe to this mod's changes

implement-spec is a skill published in the GitHub repository 51ck/frontier-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 9 tokens to every session and 437 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to implement-spec, differing in 25 lines, and is treated as a copy.

Project management

implement-spec next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
implement-spec51ck/frontier-mcp	Skill	0	1mo ago	MIT	A	9	Claude Code, Codex
imagegenopenai/codex	Skill	133k	yesterday	Apache-2.0	A	113	Codex
playwright-climicrosoft/playwright	Skill	99k	yesterday	Apache-2.0	A	19	Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	4d ago	MIT	A	200	Claude Code, Codex
systematic-debuggingobra/superpowers	Skill	313k	3d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	95	Claude Code
next-partial-prefetching-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	103	Claude Code

frontier-mcp: Skill for Claude Code