What is rest-api-scaffolder?

A scaffolding agent that creates the folder and package layout for REST API resources under an existing Python API package. Scaffolding means making the basic structure that later code will fill in.

It creates per-resource endpoint and serializer subpackages from a resource specification, without implementing the endpoint or serializer files.

It removes repetitive setup of endpoint and serializer directories while leaving implementation work to other tools.

rest-api-scaffolder — Agent for Claude Code by voro6yov

Install

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.

Clone the repo

git clone --depth 1 https://github.com/voro6yov/spec-driven-development

Made for: Claude Code.

Or install rest-api-spec, the plugin that ships this one along with the rest of its 2 skills, 15 agents.

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/agents/voro6yov/spec-driven-development/rest-api-scaffolder/github.svg)](https://agentmods.dev/agents/voro6yov/spec-driven-development/rest-api-scaffolder)

Your own site

<a href="https://agentmods.dev/agents/voro6yov/spec-driven-development/rest-api-scaffolder"><img src="https://agentmods.dev/badge/agents/voro6yov/spec-driven-development/rest-api-scaffolder/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/agents/voro6yov/spec-driven-development/rest-api-scaffolder"><img src="https://agentmods.dev/badge/agents/voro6yov/spec-driven-development/rest-api-scaffolder.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 71 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,993 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 original No closer match found 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.00071	$0.01993
Opus 5.5	$0.00028	$0.00797
Sonnet 5.5	$0.00014	$0.00399
Haiku 4.5	$0.00007	$0.00199

Measured 12d ago against content hash 7ec6a0e9aa43, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

rest-api-scaffolder 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.

plugins/rest-api-spec/agents/rest-api-scaffolder.md · 125 lines

How it starts

The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a REST API scaffolder. Your job is to install the per-surface package skeleton inside a project's api/ directory. Do not ask the user for confirmation. Be idempotent: skip anything that already exists; never overwrite existing __init__.py files.

This agent does not touch api/__init__.py, containers.py, entrypoint.py, the root api/serializers/__init__.py aggregator, or the shared serializer modules under api/serializers/ (error.py, configured_base_serializer.py, json_utils.py). Those are owned by @serializers-copier, run via /rest-api-spec:init-rest-api. It also does not implement any per-resource endpoint or serializer files. Downstream agents own that work.

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): the Markdown table emitted by @spec-core:target-locations-finder — four rows mapping Category to absolute Path and Status. Parse it as text; do not re-run the finder.

Path resolution

Recover <dir> and <stem> from <domain_diagram> at <dir>/<stem>.md per spec-core:naming-conventions. Then:

<plugin_dir> = <dir>/<stem>.rest-api
<rest_api_spec_file> = <plugin_dir>/spec.md — the resource input spec produced by the rest-api-spec:specs-generator agent, whose Table 1 (Resource Basics) supplies the surface set.

Workflow

Step 1 — Parse the locations report

From <locations_report_text>, extract the absolute Path value for the API Package row and bind it to <api_pkg>. All other rows are ignored.

If the row is missing or its path is empty, fail with: Error: API Package row missing from locations report.

Step 2 — Read the rest-api spec file and extract the surface list + aggregate

Read <rest_api_spec_file>.

If the file does not exist, fail with: Error: rest-api spec file not found at <rest_api_spec_file>. Run @rest-api-spec:specs-generator first.
If the file does not contain a ### Table 1: Resource Basics heading, fail with: Error: <rest_api_spec_file> is malformed — missing 'Table 1: Resource Basics'.

Read the full file on GitHub · 125 lines

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.

12d ago First seen · 125 lines · 71 tokens per session scan A 7ec6a0e9aa43

Subscribe to this mod's changes

rest-api-scaffolder is an agent published in the GitHub repository voro6yov/spec-driven-development (5 stars, last pushed 12d ago), licensed Apache-2.0. It adds 71 tokens to every session and 1,993 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-10-04.

Backend and APIs

php-developer

Write idiomatic PHP code with design patterns, SOLID principles, and modern best practices. Implements PSR standards, dependency injection, and comprehensive testing. Use PROACTIVELY for PHP architecture, refactoring, or implementing design patterns.

davepoon/buildwithclaude · 51 tokens

backend-reviewer

Use when reviewing service-layer logic, module boundaries, business rules, or cross-service contracts — verifies architecture integrity and service correctness against the api and architect persona standards.

jeremylongshore/tons-of-skills-marketplace · 36 tokens

integrations-engineer

Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…

avelikiy/great_cto · 106 tokens

gate

API quality gates — linting, style enforcement, breaking change CI, and API governance.

tonone-ai/tonone · 19 tokens

broadcasting-agent

Creates WebSocket broadcasting infrastructure (NestJS backend) and real-time consumption on the frontend (Next.js or React). Use when adding real-time event broadcasting to a bounded context, creating Socket.IO gateways, or implementing frontend event listeners. Dispatched after infrastructure layer is complete.

Softtor/nestjs-hexagonal · 58 tokens

dotnet-architecture-reviewer

Reviews a .NET codebase or repository and produces a structured architecture report — layering and dependency-rule violations, coupling, CQRS/handler hygiene, EF Core boundary leaks, testability, and concrete prioritized fixes. Use when the user wants an architecture review, a "second opinion" on structure, a PR-level…

StefanTheCode/dotnet-ai-toolkit · 102 tokens