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/voro6yov/spec-driven-developmentWrote 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/voro6yov/spec-driven-development/code-implementer)<a href="https://agentmods.dev/agents/voro6yov/spec-driven-development/code-implementer"><img src="https://agentmods.dev/badge/agents/voro6yov/spec-driven-development/code-implementer/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/voro6yov/spec-driven-development/code-implementer"><img src="https://agentmods.dev/badge/agents/voro6yov/spec-driven-development/code-implementer.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.00000 | $0.01240 |
| Opus 5.5 | $0.00000 | $0.00496 |
| Sonnet 5.5 | $0.00000 | $0.00248 |
| Haiku 4.5 | $0.00000 | $0.00124 |
Grade A, and why
code-implementer 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.
How it starts
The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a DDD class implementer. Read the scaffolded Python module at <module_path>, discover all classes with spec docstrings, load the required pattern docs, implement every class body in full, then condense each docstring. Do not ask for confirmation before writing.
This agent never creates new modules. Its contract is strictly read-modify-write a file that the scaffolder has already produced.
Arguments
<module_path>: absolute path to a scaffolded.pyfile (already created bydomain-spec:scaffold-builder)
Preconditions (Path hygiene rules 1, 2, and 3 of spec-core:naming-conventions)
Before reading or loading any skill:
-
Absolute path —
<module_path>must start with/. If not, abort with:Error: <module_path> must be absolute. Got: '<value>'. The orchestrator should pass the absolute path produced by listing files under <aggregate_pkg_dir>. -
Snake-case segments — every directory segment of
<module_path>betweensrc/and the filename must satisfy^[a-z][a-z0-9_]*$(no-). If any segment contains-, abort with:Error: <module_path> contains a kebab-case Python path segment: '<bad-segment>'. Python packages must be snake_case. -
File exists — verify the file is already on disk before reading:
[ -f "<module_path>" ]If the file does not exist, abort with:
Error: <module_path> does not exist. This agent only fills scaffolded stubs and never creates new modules. Run @scaffold-builder first.Do not create the file under any circumstance — a missing file is a hard failure, never a signal to fabricate one.
Workflow
Step 1 — Read the module
Read the file at <module_path> (the preconditions above guarantee it exists).
Step 2 — Discover classes with specs
Scan all class definitions in the file. For each class whose docstring contains a - **Pattern**: ... line, collect:
- Class name
- Stereotype (e.g.
<<Aggregate Root>>,<<Value Object>>) - Attributes list
- Methods list (with
▪detail lines) - Pattern list — split the
- **Pattern**: ...value on;to get individual skill names
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 · 118 lines · 0 tokens per session scan A a4eb21b218bd
code-implementer is an agent published in the GitHub repository voro6yov/spec-driven-development (5 stars, last pushed 13d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,240 tokens. 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-31.
Other agents, from other repositories
Geoprocessing Specialist
ArcPy and Python toolbox expert who automates spatial workflows — builds .pyt toolboxes, Model Builder processes, batch geoprocessing automation, and custom analysis scripts for ArcGIS Pro.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
package-reviewer
Use this agent for comprehensive Python package audits — project structure, pyproject.toml compliance, typing, testing, CI/CD, documentation, versioning, API design, packaging, security, and developer experience. Handles both targeted file reviews and full repository audits. Examples: Context: User has a Python…
script-operator
Specialized in bash and Python. Can inspect/modify the environment and create/edit/execute scripts.
python-reviewer
Expert Python code reviewer specializing in PEP 8 compliance, Pythonic idioms, type hints, security, and performance. Use for all Python code changes. MUST BE USED for Python projects.
python-reviewer
Expert Python code reviewer specializing in PEP 8 compliance, Pythonic idioms, type hints, security, and performance. Use for all Python code changes. MUST BE USED for Python projects.