new-service

new-service is a skill for Claude Code from voro6yov/spec-driven-development. It costs 109 tokens per session (1,928 once invoked), scanned A, original, Apache-2.0.

A skill that creates a new spec-driven Python service repository from command-line options. It can include or omit persistence, REST, and messaging layers.

In plain words
What is it for?
It creates a uv project with optional PostgreSQL and SQLAlchemy persistence, FastAPI REST support, RabbitMQ messaging, Docker and Compose files, and Liquibase migrations.
Why use it?
It removes the repeated setup needed to start a service with a consistent source layout, infrastructure files, and runtime foundations.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the AskUserQuestion tool.

Part of the project-scaffold plugin — 1 skill shipped together

Good fit It creates a uv project with optional PostgreSQL and SQLAlchemy persistence, FastAPI REST support, RabbitMQ messaging, Docker and Compose files, and Liquibase migrations.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/voro6yov/spec-driven-development/new-service
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.

Any agent
npx skills add voro6yov/spec-driven-development --skill new-service
Clone the repo
git clone --depth 1 https://github.com/voro6yov/spec-driven-development

Made for: Claude Code.

Or install project-scaffold, the plugin that ships this one along with the rest of its 1 skill.

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.

agentmods badge for new-service

README.md
[![agentmods](https://agentmods.dev/badge/skills/voro6yov/spec-driven-development/new-service/github.svg)](https://agentmods.dev/skills/voro6yov/spec-driven-development/new-service)
Your own site
<a href="https://agentmods.dev/skills/voro6yov/spec-driven-development/new-service"><img src="https://agentmods.dev/badge/skills/voro6yov/spec-driven-development/new-service/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.

agentmods 80×15 button for new-service

Your own site · 80×15
<a href="https://agentmods.dev/skills/voro6yov/spec-driven-development/new-service"><img src="https://agentmods.dev/badge/skills/voro6yov/spec-driven-development/new-service.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 109 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,928 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00109 $0.01928
Opus 5.5 $0.00044 $0.00771
Sonnet 5.5 $0.00022 $0.00386
Haiku 4.5 $0.00011 $0.00193

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

Security

Grade A, and why

new-service 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.

The scan reads SKILL.md. This mod also ships 18 executable files (scaffold.py, templates/etc/migrator/entrypoint.sh, templates/src/pkg/__init__.py, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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/project-scaffold/skills/new-service/SKILL.md · 113 lines

How it starts

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

You scaffold a new service repository. The tree is rendered by scaffold.py — a deterministic, stdlib-only script that ships next to this file — never by hand. Your job is to collect the inputs, run the script, initialize the spec layers, verify, commit, and report. Do not write or edit any generated file yourself.

Inputs

$ARGUMENTS is <service-name> followed by optional flags, passed through to the script verbatim:

Argument Meaning Default
<service-name> kebab-case name; the new directory and the uv project name — (required)
--package PKG importable package under src/ snake_case of the name
--python X.Y CPython minor version (3.11+) 3.12
--port N HTTP port of the API process 8000
--no-persistence omit Postgres/SQLAlchemy, Datasources, the Liquibase migrator layer on
--no-rest omit FastAPI, the api/ package, create_fastapi/run_api, the serve command layer on
--no-messaging omit RabbitMQ, the vendored pubsub, the Messaging/MessageBrokers containers layer on
--dry-run print the planned tree; write nothing off

The service is created in the current working directory as ./<service-name>. The script refuses if that path exists — it never overwrites.

If $ARGUMENTS is empty, use AskUserQuestion once to collect the service name and which layers to include, then continue. Never ask when a name was given — the flags have defaults.

Workflow

Step 1 — Resolve the two directories

  • <skill_dir> — the directory containing this SKILL.md (shown when the skill loads). The script is <skill_dir>/scaffold.py.
  • <modules_dir> — invoke the spec-core:modules skill via the Skill tool and take the directory containing its SKILL.md. If spec-core is not installed, stop with ERROR: the spec-core plugin is required (spec-core:modules supplies the vendored runtime modules).

Step 2 — Render

python3 "<skill_dir>/scaffold.py" $ARGUMENTS --modules-dir "<modules_dir>"

Read the full file on GitHub · 113 lines

Files

What ships with it

31 files 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.

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.

  1. 12d ago First seen · 113 lines · 109 tokens per session scan A 8927c9a2a074

Subscribe to this mod's changes

new-service is a skill published in the GitHub repository voro6yov/spec-driven-development (5 stars, last pushed 13d ago), licensed Apache-2.0. It adds 109 tokens to every session and 1,928 once invoked, about $0.0004 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.