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 skills add martinffx/atelier --skill spec-implementgit clone --depth 1 https://github.com/martinffx/atelierWrote 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/skills/martinffx/atelier/spec-implement)<a href="https://agentmods.dev/skills/martinffx/atelier/spec-implement"><img src="https://agentmods.dev/badge/skills/martinffx/atelier/spec-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.
<a href="https://agentmods.dev/skills/martinffx/atelier/spec-implement"><img src="https://agentmods.dev/badge/skills/martinffx/atelier/spec-implement.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00063 | $0.02303 |
| Opus 5.5 | $0.00025 | $0.00921 |
| Sonnet 5.5 | $0.00013 | $0.00461 |
| Haiku 4.5 | $0.00006 | $0.00230 |
Grade A, and why
spec-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 today.
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 — 311 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec Implement
Execute the approved Spec-backed Plan. Track progress when it uses tracked tasks. Report. Stop when blocked.
Announce at start: "I'm using the spec-implement skill to execute this plan."
This skill does not make design decisions or change approved content. It may persist approved content from the conversation when Plan Mode could not write the required artifact. If the plan is wrong, go back to spec-plan. If the design is wrong, go back to spec-brainstorm.
Prerequisites
Resolve required artifacts in order before starting product implementation:
- If
docs/specs/YYYY-MM-DD-<feature>/design.mdis missing, write it from the approved design in the current conversation. Validate the file, report its path, and stop. Do not createplan.jsonor start implementation in the same invocation. - Otherwise, if
docs/specs/YYYY-MM-DD-<feature>/plan.jsonis missing, write it from the approved plan in the current conversation. Validate it against the schema inspec-plan, report its path, and stop. Do not start implementation in the same invocation. - If the approved content needed for the next missing artifact is not available in the current conversation, stop and tell the human what content is unavailable. Do not ask the human to create the file.
- When both artifacts exist, verify that any tracker entries selected during planning are
available, along with
docs/agents/issue-tracker.mdwhen tracking is configured. - Verify that you are not on main/master without explicit user consent. Create a branch or use a git worktree first.
Each invocation creates at most one missing artifact. Only proceed to product implementation when both approved artifacts existed at the start of the invocation.
Step 1: Load and Review the Plan
Read plan.json critically before writing code. Look for:
- Unclear or ambiguous tasks
- Missing file paths or incomplete validation criteria
- Tasks that conflict with each other
- Dependencies that don't match what you see in the codebase
- Existing code or platform behavior that already satisfies a planned capability
- Duplicate IDs, parsers, errors, schemas, lifecycle handling, or test utilities
- Shared abstractions with fewer than two current consumers
- Tests whose only purpose is validating a new wrapper
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.
- today Changed 4cee48faf8c8
- 8d ago Changed · +13 lines 035ae8ef356d
- 1mo ago First seen · 298 lines · 63 tokens per session scan A 7ed8e3cd3c16
spec-implement is a skill published in the GitHub repository martinffx/atelier (47 stars, last pushed today), licensed MIT. It adds 63 tokens to every session and 2,303 once invoked, about $0.0003 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 skills, from other repositories
java-code-style
A Java code-style guide and review workflow for teams working with Java and Spring Boot applications.
python-pro
Use when building Python 3.11+ applications requiring type safety, async programming, or robust error handling. Generates type-annotated Python code, configures mypy in strict mode, writes pytest test suites with fixtures and mocking, and validates code with black and ruff. Invoke for type hints, async/await patterns…
ralph
Self-referential loop until task completion with configurable verification reviewer.
self-improve
Autonomous evolutionary code improvement engine with tournament selection.
harbor
Harbor intake for external work — the captain only handles unresolved decisions. Sweeps incoming issues and PRs, verifies every claim before disposition, reuses every decision already made, and hands the maintainer a docket whose pending items each carry one question with options, recommendation, impact and evidence.…
autoresearch
Stateful single-mission improvement loop with strict evaluator contract, markdown decision logs, and max-runtime stop behavior.