scaffold-archipy-service

scaffold-archipy-service is a skill for Claude Code from SyntaxArc/archipy-plugin. It costs 52 tokens per session (492 once invoked), scanned A, a copy of safe-markdown-auto-fix, MIT.

A code scaffold for adding an ArchiPy service, meaning the part of an application that exposes functionality over HTTP or gRPC. It covers both FastAPI, a Python web framework, and gRPC, a system for services to communicate with each other.

In plain words
What is it for?
Use it when adding a versioned HTTP or gRPC endpoint under a domain, including the router or service handler and the application's startup wiring.
Why use it?
It helps keep the service layer thin and connected to the application's existing startup and configuration code, instead of mixing web or network details with business rules.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the archipy plugin — 12 skills, 19 commands shipped together

Good fit Use it when adding a versioned HTTP or gRPC endpoint under a domain, including the router or service handler and the application's startup wiring.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/syntaxarc/archipy-plugin/scaffold-archipy-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 SyntaxArc/archipy-plugin --skill scaffold-archipy-service
Clone the repo
git clone --depth 1 https://github.com/SyntaxArc/archipy-plugin

Made for: Claude Code.

Or install archipy, the plugin that ships this one along with the rest of its 12 skills, 19 commands.

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 scaffold-archipy-service

README.md
[![agentmods](https://agentmods.dev/badge/skills/syntaxarc/archipy-plugin/scaffold-archipy-service.svg)](https://agentmods.dev/skills/syntaxarc/archipy-plugin/scaffold-archipy-service)
Your own site
<a href="https://agentmods.dev/skills/syntaxarc/archipy-plugin/scaffold-archipy-service"><img src="https://agentmods.dev/badge/skills/syntaxarc/archipy-plugin/scaffold-archipy-service.svg" alt="Measured on agentmods" height="20"></a>
Per session 52 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 492 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 86% copy Near-identical to another mod 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.00052 $0.00492
Opus 5 $0.00026 $0.00246
Sonnet 5 $0.00010 $0.00098
Haiku 4.5 $0.00005 $0.00049

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

Security

Grade A, and why

scaffold-archipy-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 7d 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.

Origin

This is a copy

86% identical to safe-markdown-auto-fix — 117 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/scaffold-archipy-service/SKILL.md · 69 lines

What it actually says

Scaffold ArchiPy Service

Before writing files

Ask the user for:

  1. Domain name (e.g. user)
  2. API version (default v1)
  3. Transport: FastAPI (default) or gRPC (sync vs async)

Prefer ArchiPy

uv add "archipy[fastapi]"   # HTTP
uv add "archipy[grpc]"      # gRPC

Generate

services/<domain>/v{n}/
└── <domain>_service.py

FastAPI

  • Thin router: request → domain *InputDTO → logic → *OutputDTO.
  • Export create_router(container) (or equivalent) for manage.py / app factory.
  • Map domain errors to HTTP status; no business rules / atomic UoW decorators here.

gRPC

  • Thin servicer calling logic; sync servicers with AppUtils.create_grpc_app, async with create_async_grpc_app.
  • Do not mix sync/async servicer styles on one server.

Bootstrap (entrypoint)

Prefer AppUtils — do not hand-roll bare FastAPI() / grpc.server():

from archipy.helpers.utils.app_utils import AppUtils
from archipy.configs.base_config import BaseConfig

app = AppUtils.create_fastapi_app()
app.include_router(create_user_v1_router(container))

uvicorn in manage.py from config.FASTAPI (SERVE_HOST, SERVE_PORT, RELOAD, PROXY_HEADERS, FORWARDED_ALLOW_IPS).

Constraints

  • Version in path (v1, v2), not in business logic.
  • Do not re-implement CORS/exception handlers/stock gRPC interceptors AppUtils already wires.
  • Wire logic via DI container.

Docs

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. 7d ago First seen · 69 lines · 52 tokens per session scan A 0e0430cf30e8

Subscribe to this mod's changes

scaffold-archipy-service is a skill published in the GitHub repository SyntaxArc/archipy-plugin (2 stars, last pushed 14d ago), licensed MIT. It adds 52 tokens to every session and 492 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to safe-markdown-auto-fix, differing in 117 lines, and is treated as a copy.

Related

Other skills, from other repositories

fastapi-templates

Create production-ready FastAPI projects with async patterns, dependency injection, and comprehensive error handling. Use when building new FastAPI applications or setting up backend API projects.

wshobson/agents · 37 tokens

telnyx-numbers-python

Search, order, and manage phone numbers by location, features, and coverage.

team-telnyx/ai · 23 tokens

telnyx-ai-outbound-voice-python

End-to-end setup for making a Telnyx AI assistant call a phone number. Covers provisioning a phone number, creating a TeXML application, assigning the number, configuring telephony settings, whitelisting destination countries, and triggering outbound calls via scheduled events. Use this skill (not…

team-telnyx/ai · 97 tokens

specx-component-architecture

Design or review specx core scope boundaries in Python services. Use when deciding where code belongs across packaged scoped foundation bases, optional local foundation extensions, core/, capabilities, delivery, infrastructure, shared/, and ioc; when adding guardrails or splitting use cases, services, DTOs, schemas…

maksimzayats/specx · 74 tokens

specx-project-structure

Create or reshape a Python FastAPI service repo into the specx clean core/delivery architecture using packaged scoped foundation bases. Use when starting an API backend, adding the first src package, or establishing AGENTS.md, core/, optional local foundation/, delivery/, infrastructure, ioc/, migrations, and tests.

maksimzayats/specx · 75 tokens

specx-add-core-use-case

Add or refactor a specx core scope use case. Use when implementing an externally meaningful application action under a core scope usecases package, adding same-file command/query inputs, result DTOs, coordinating services, opening a unit-of-work transaction, or moving behavior out of delivery or infrastructure into…

maksimzayats/specx · 70 tokens