specx-add-delivery-controller

specx-add-delivery-controller is a skill for Codex from maksimzayats/specx. It costs 73 tokens per session (605 once invoked), scanned A, original, MIT.

A guide for adding the HTTP-facing part of a specx Python service, especially routes built with FastAPI. It covers controllers, request and response data, application startup and shutdown, and delivery-layer checks such as authentication and rate limits.

In plain words
What is it for?
Use it to add FastAPI endpoints, define their input and output shapes, connect routes to application actions, register them, manage application lifecycle events, and translate errors into HTTP responses.
Why use it?
It keeps web-facing code separate from the service's core work and gives requests and errors a consistent path into the application. This makes route code easier to organize and maintain.

Skill for Codex

Written for Codex: agents/openai.yaml present. Also seen: installed under .agents/ (shared by several agents).

Good fit Use it to add FastAPI endpoints, define their input and output shapes, connect routes to application actions, register them, manage application lifecycle events, and translate errors into HTTP responses.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/maksimzayats/specx/specx-add-delivery-controller
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 maksimzayats/specx --skill specx-add-delivery-controller
Clone the repo
git clone --depth 1 https://github.com/maksimzayats/specx

Made for: Codex.

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 specx-add-delivery-controller

README.md
[![agentmods](https://agentmods.dev/badge/skills/maksimzayats/specx/specx-add-delivery-controller/github.svg)](https://agentmods.dev/skills/maksimzayats/specx/specx-add-delivery-controller)
Your own site
<a href="https://agentmods.dev/skills/maksimzayats/specx/specx-add-delivery-controller"><img src="https://agentmods.dev/badge/skills/maksimzayats/specx/specx-add-delivery-controller/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 specx-add-delivery-controller

Your own site · 80×15
<a href="https://agentmods.dev/skills/maksimzayats/specx/specx-add-delivery-controller"><img src="https://agentmods.dev/badge/skills/maksimzayats/specx/specx-add-delivery-controller.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 73 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 605 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00073 $0.00605
Opus 5 $0.00036 $0.00302
Sonnet 5 $0.00015 $0.00121
Haiku 4.5 $0.00007 $0.00060

Measured 10d ago against content hash 85a6a3e47d23, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

specx-add-delivery-controller 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 10d 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.

.agents/skills/specx-add-delivery-controller/SKILL.md · 54 lines

How it starts

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

specx Add Delivery Controller

Use this skill at the framework boundary. Read references/controller.md before adding controller code.

Workflow

  1. Put controllers under delivery/fastapi/controllers/<scope>.py.
  2. Put request and response schemas under delivery/fastapi/schemas/.
  3. Use one controller per scoped set of use cases, for example TasksController for create/get/list task routes.
  4. Put controller-only helpers such as auth dependencies, rate limiters, and request-context readers under delivery/fastapi/services/.
  5. Make controllers inherit BaseController, schemas inherit BaseFastAPISchema, delivery helpers inherit BaseDeliveryService, and FastAPI lifespan managers inherit BaseLifecycle[FastAPI].
  6. Add docstrings with scope and a concrete Example: to controllers, schemas, and delivery services.
  7. Inject use cases or delivery services with Injected[...]. A simple delivery-owned /healthz response needs no core workflow; inject core/health use cases when readiness checks a required external dependency or probe policy is reused across deliveries.
  8. Map request schema/path data into the use case's same-file Command or Query input.
  9. Call the use case.
  10. Map the result into a response schema.
  11. Declare the success status explicitly when it is not 200, such as 201 for a resource-creating POST or 204 for a response with no body.
  12. Translate known application exceptions into stable, non-sensitive HTTP responses. Do not expose raw exception messages.
  13. Register full public business route paths such as /api/v1/users. Do not split API prefixes across routers and route fragments. Operational probes are the only unversioned exception: /healthz and /readyz.
  14. For FastAPI apps with long-lived resources, inject FastAPILifecycle into the app factory and pass it to FastAPI(lifespan=...).
  15. Add integration tests at the HTTP boundary, including the declared success code and each translated application error.

Read the full file on GitHub · 54 lines

Files

What ships with it

2 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. 10d ago First seen · 54 lines · 73 tokens per session scan A 85a6a3e47d23

Subscribe to this mod's changes

specx-add-delivery-controller is a skill published in the GitHub repository maksimzayats/specx (201 stars, last pushed 1mo ago), licensed MIT. It adds 73 tokens to every session and 605 once invoked, about $0.0004 per session on Opus 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-08-30.

Related

Other skills, from other repositories

spec-kitty-orchestrator-api-operator

Teach agents and external systems how to use spec-kitty orchestrator-api to drive workflows from outside the host CLI. Triggers: "use orchestrator-api", "build a custom orchestrator", "automate externally", "integrate CI with spec-kitty", "call spec-kitty from another tool", "orchestrator contract", "external…

Priivacy-ai/spec-kitty · 125 tokens

api-design

Design or review an HTTP/REST/GraphQL API for versioning, pagination, error shapes, idempotency, auth, status codes, cache headers, and breaking-change management. Use when asked to "design an API", "shape the endpoints", "design the schema", "add a new endpoint", "review this API", or when building/modifying a public…

open-gsd/gsd-pi · 91 tokens

create-mcp-server

Build, iterate, and evaluate Model Context Protocol (MCP) servers that expose external services as tools an LLM can call. Covers schema/tool design, error handling, pagination, MCP Inspector testing, and an eval set. Use when asked to "build an MCP server", "create an MCP tool", "wrap this API as MCP", "expose X to…

open-gsd/gsd-pi · 90 tokens

spk-integrate-orchestrator-api

Use Spec Kitty orchestrator-api from external systems, respecting host boundaries, state contracts, and workflow commands.

Priivacy-ai/spec-kitty · 30 tokens

backend-conventions

Backend convention reference (.NET 10 / C# 13). Auto-injected into backend-aware agents - not user-invocable.

fpindej/netrock · 27 tokens

architecture-patterns

Architecture validation and patterns for clean architecture, backend structure enforcement, project structure validation, test standards, and context-aware sizing. Use when designing system boundaries, enforcing layered architecture, validating project structure, defining test standards, or choosing the right…

yonatangross/orchestkit · 56 tokens