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/wojcikmm/spec-development-protocol/create-api-endpointnpx skills add WojcikMM/spec-development-protocol --skill create-api-endpointgit clone --depth 1 https://github.com/WojcikMM/spec-development-protocolWhat 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.00018 | $0.00328 |
| Opus 5 | $0.00009 | $0.00164 |
| Sonnet 5 | $0.00004 | $0.00066 |
| Haiku 4.5 | $0.00002 | $0.00033 |
Grade A, and why
create-api-endpoint 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.
What it actually says
Skill: Create REST API Endpoint
Purpose
Produce a consistent, secure, and documented HTTP endpoint that meets its design contract.
Prerequisites
- API contract (path, method, schemas) is defined in the design spec.
- Auth requirements are specified.
Checklist
- Route: Use plural nouns for resources (
/users) and correct HTTP methods (GET, POST, etc.). - Input Validation: Reject invalid input immediately with a
400 Bad Request. Use a schema validation library. - Auth: Apply auth middleware to non-public routes. Check resource-level permissions. Return
401(unauthenticated) or403(unauthorized). - Business Logic: Delegate logic to a service layer. Keep route handlers thin. Handle
404 Not Foundexplicitly. - Error Handling: Never expose stack traces. Use a consistent error response shape. Log errors with a trace ID.
- Response: Return correct status codes (
200,201,204, etc.). IncludeLocationheader for201 Created. Use DTOs to avoid over-exposing data. - Documentation: Update OpenAPI/Swagger spec.
Quality Bar
- Rejects invalid input with
400. - Covered by integration tests (happy path + error path).
- No internal details (secrets, stack traces) leak in responses.
- Auth is enforced and tested.
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 · 33 lines · 18 tokens per session scan A c4fc69439c69
create-api-endpoint is a skill published in the GitHub repository WojcikMM/spec-development-protocol (2 stars, last pushed 22d ago), licensed MIT. It adds 18 tokens to every session and 328 once invoked, about $0.0001 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-31.
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.
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.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…