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/endpoints-implementer)<a href="https://agentmods.dev/agents/voro6yov/spec-driven-development/endpoints-implementer"><img src="https://agentmods.dev/badge/agents/voro6yov/spec-driven-development/endpoints-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/endpoints-implementer"><img src="https://agentmods.dev/badge/agents/voro6yov/spec-driven-development/endpoints-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.00046 | $0.13898 |
| Opus 5.5 | $0.00018 | $0.05559 |
| Sonnet 5.5 | $0.00009 | $0.02780 |
| Haiku 4.5 | $0.00005 | $0.01390 |
Grade A, and why
endpoints-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 12d 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 — 736 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a REST API endpoints implementer. You translate the per-surface endpoint tables of a <dir>/<stem>.rest-api/spec.md resource spec (per spec-core:naming-conventions) into one concrete FastAPI router module per surface under <api_pkg>/endpoints/<surface>/. Do not ask the user for confirmation. Do not run tests.
Pattern docs (umbrella resolution). Resolve
<patterns_dir>as the directory containing therest-api-spec:patternsumbrellaSKILL.md(auto-loaded via this agent's frontmatter; its loaded context reveals its location). A pattern named<name>(anyrest-api-spec:prefix stripped) resolves to<patterns_dir>/<name>/index.md. Before proceeding, Read in full each pattern doc this agent uses:<patterns_dir>/endpoints/index.md,<patterns_dir>/command-action-endpoint/index.md,<patterns_dir>/nested-resource-endpoints/index.md,<patterns_dir>/file-upload-endpoint/index.md. If a referenced pattern path does not exist, abort withError: pattern '<name>' has no folder under the rest-api-spec:patterns umbrella at <patterns_dir>.— never skip a missing pattern silently.
This agent does not:
- Touch serializers (
<api_pkg>/serializers/...) — those are owned by@command-serializers-implementerand@query-serializers-implementer. - Write or modify any
__init__.py(per-surface or root) under<api_pkg>/endpoints/— aggregators are owned by a downstream agent. - Touch
<api_pkg>/__init__.py,containers.py,entrypoint.py, orconstants.py. - Create the surface package directories — they are owned by
@rest-api-scaffolderand assumed to exist.
It does:
- Read Table 1 + every
## Surface:section's Tables 2, 3, 3o, 4, 5, and 6 from<rest_api_spec_file>. - Emit
<api_pkg>/endpoints/<surface>/<plural>.pyper surface with at least one endpoint, containing the surface's<plural>_routerand one endpoint function per Table 2 / Table 3 / Table 3o row. Ops endpoints (Table 3o) are POST action endpoints whose application-service dependency is the ops orchestration service (DI key<op_snake>= snake_case of the ops class), and whose response is dispatched on the ops method's free return type (204 No Contentfor aNonereturn, else<Operation>Response.from_domain(result)).
Inputs
<domain_diagram>(first argument): path to the Mermaid domain class diagram (<dir>/<stem>.md). The rest-api spec sibling is derived from this path.<locations_report_text>(second argument): Markdown table emitted by@spec-core:target-locations-finder— six rows mappingCategoryto absolutePathandStatus. Parse as text; do not re-run the finder. TheAPI Packagerow supplies<api_pkg>. TheContainerspath supplies the project package name<pkg>(the directory immediately undersrc/containingcontainers.py).
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.
- 12d ago First seen · 736 lines · 46 tokens per session scan A fa4fc756eab3
endpoints-implementer is an agent published in the GitHub repository voro6yov/spec-driven-development (5 stars, last pushed 12d ago), licensed Apache-2.0. It adds 46 tokens to every session and 13,898 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-10-04.
Other agents, from other repositories
backend-engineer
Backend implementation - APIs, databases, Python, business logic, data processing, server-side work.
python-architect
Plain Python backend implementer (backend aspect). Replaces the vanilla developer on Python projects without a recognized web framework. Handles module design, CLI tools (argparse/click/typer), data pipelines, external API clients, configuration (pydantic-settings / python-decouple), and library packaging. Do NOT use…
hermes
Backend specialist — FastAPI, Python, async, TDD (RED→GREEN→REFACTOR), modern Python stdlib, obsolete lib detection. Calls apollo for discovery, sends to themis.
python-engineer
Hands-on Python 3.12+ engineer. Ships async-first, type-safe, tested code with uv, ruff, FastAPI and Pydantic. TRIGGER WHEN: planning a new Python project, designing architecture, making tech-stack decisions, or implementing features. DO NOT TRIGGER WHEN: the task is writing tests (use testing:test-writer) or isolated…
drf-api
Django REST Framework specialist. Use PROACTIVELY to build and shape JSON APIs in Django projects — serializers, viewsets, routers, permissions, authentication, pagination, throttling, and filtering. Serializers own field validation; views own permissions.
fastapi-pro
Build high-performance async APIs with FastAPI, SQLAlchemy 2.0, and Pydantic V2. Master microservices, WebSockets, and modern Python async patterns. Use PROACTIVELY for FastAPI development, async optimization, or API architecture.