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/bdiasti/maestro-bundle-cli/api-designnpx skills add bdiasti/maestro-bundle-cli --skill api-designgit clone --depth 1 https://github.com/bdiasti/maestro-bundle-cliWhat 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.00040 | $0.01665 |
| Opus 5 | $0.00020 | $0.00833 |
| Sonnet 5 | $0.00008 | $0.00333 |
| Haiku 4.5 | $0.00004 | $0.00167 |
Grade C, and why
api-design scanned grade C with 2 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
curl -s http://localhost:8000/api/v1/demands?page=1&size=10 | python -m json.tool Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s http://localhost:8000/api/v1/demands?page=1&size=10 | python -m json.tool How it starts
The opening of the file, as written. The whole thing — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API Design
Build production-ready REST APIs with standardized patterns for routing, pagination, error handling, versioning, and OpenAPI documentation.
When to Use
- Creating new REST API endpoints
- Defining API contracts and response schemas
- Adding pagination, filtering, or sorting to list endpoints
- Implementing standardized error handling
- Setting up API versioning strategy
- Generating OpenAPI/Swagger documentation
Available Operations
- Create CRUD endpoints with FastAPI
- Define request/response models with Pydantic
- Implement standardized error handling
- Add pagination to list endpoints
- Configure API versioning
- Generate and validate OpenAPI documentation
Multi-Step Workflow
Step 1: Define the REST Contract
Map business operations to HTTP methods and paths.
| Operation | Method | Path | Status | Body |
|---|---|---|---|---|
| List | GET | /api/v1/demands |
200 | Paginated list |
| Get | GET | /api/v1/demands/{id} |
200 | Single object |
| Create | POST | /api/v1/demands |
201 | Created object |
| Update | PUT | /api/v1/demands/{id} |
200 | Updated object |
| Patch | PATCH | /api/v1/demands/{id} |
200 | Updated object |
| Delete | DELETE | /api/v1/demands/{id} |
204 | Empty |
Step 2: Create the Controller with FastAPI
from fastapi import APIRouter, Depends, HTTPException, Query
router = APIRouter(prefix="/api/v1/demands", tags=["demands"])
@router.get("/", response_model=PaginatedResponse[DemandResponse])
async def list_demands(
page: int = Query(1, ge=1),
size: int = Query(20, ge=1, le=100),
status: str | None = None,
use_case: ListDemands = Depends()
):
result = use_case.execute(page=page, size=size, status=status)
return PaginatedResponse(
items=result.items,
total=result.total,
page=page,
size=size
)
@router.post("/", response_model=DemandResponse, status_code=201)
async def create_demand(
body: CreateDemandRequest,
use_case: CreateDemand = Depends()
):
return use_case.execute(body)
@router.get("/{demand_id}", response_model=DemandResponse)
async def get_demand(
demand_id: str,
use_case: GetDemand = Depends()
):
result = use_case.execute(demand_id)
if not result:
raise HTTPException(status_code=404, detail="Demand not found")
return result
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.
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 · 210 lines · 40 tokens per session scan C db901a078f42
api-design is a skill published in the GitHub repository bdiasti/maestro-bundle-cli (21 stars, last pushed 5mo ago), licensed MIT. It adds 40 tokens to every session and 1,665 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). 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.