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.
npx agentmods add skills/ocbunknown/fastapi-claude-template/usecasenpx skills add ocbunknown/fastapi-claude-template --skill usecasegit clone --depth 1 https://github.com/ocbunknown/fastapi-claude-templateWhat 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 | $0.00081 | $0.02841 |
| Opus 5 | $0.00041 | $0.01421 |
| Sonnet 5 | $0.00016 | $0.00568 |
| Haiku 4.5 | $0.00008 | $0.00284 |
Grade A, and why
usecase 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 2d 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 — 227 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writing use cases (src/application/v1/usecases/<domain>/)
A use case is the transport-agnostic unit of business logic. Endpoints, consumers, and scheduled tasks all call request_bus.send(Request(...)) and get back a Result. Use cases never know who called them.
One file, two classes
Every use case file defines exactly one Request class and exactly one UseCase class. Keep them in the same file — they are a pair.
# src/application/v1/usecases/widget/create.py
from dataclasses import dataclass
from typing import Annotated
import uuid_utils.compat as uuid
from pydantic import Field
from src.application.common.interfaces.usecase import UseCase
from src.application.common.request import Request
from src.application.v1.results import WidgetResult
from src.database.psql import DBGateway
class CreateWidgetRequest(Request):
name: Annotated[str, Field(max_length=64)]
owner_uuid: uuid.UUID
@dataclass(slots=True)
class CreateWidgetUseCase(UseCase[CreateWidgetRequest, WidgetResult]):
database: DBGateway
async def __call__(self, request: CreateWidgetRequest) -> WidgetResult:
async with self.database:
widget = (
await self.database.widget.create(
name=request.name,
owner_uuid=request.owner_uuid,
)
).result()
return WidgetResult(**widget.as_dict())
Invariants
Requestinheritssrc.application.common.request.Request(Pydantic,frozen=True). Validation viaAnnotated[..., Field(...)]. Do not reuse HTTPContractclasses here — the Request describes the use-case input, not the HTTP input.UseCaseinheritsUseCase[RequestClass, ReturnType]. The base class auto-applies@dataclass(slots=True)— add your own@dataclass(slots=True)on the subclass too for mypy/readability.- Dependencies are dataclass fields:
database: DBGateway,hasher: Hasher,cache: StrCache,services: ServiceGateway, etc. Injected by Dishka via the request bus — do not instantiate manually. - Returns a
Resultsubclass fromsrc/application/v1/results/— never aContractfrompresentation/, never a bare ORM model, never a dict. - Register the use case in
src/application/v1/usecases/__init__.py::setup_use_cases():request_bus.register(widget.CreateWidgetRequest, widget.CreateWidgetUseCase) - Re-export from
src/application/v1/usecases/widget/__init__.pyso the presentation/consumers layer can importfrom src.application.v1.usecases.widget import CreateWidgetRequest.
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.
- 2d ago First seen · 227 lines · 81 tokens per session scan A 71209159bc06
usecase is a skill published in the GitHub repository ocbunknown/fastapi-claude-template (32 stars, last pushed 4mo ago), licensed MIT. It adds 81 tokens to every session and 2,841 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.