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 skills add zakelfassi/skills-driven-development --skill api-endpointgit clone --depth 1 https://github.com/zakelfassi/skills-driven-developmentWrote 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.
[](https://agentmods.dev/skills/zakelfassi/skills-driven-development/api-endpoint)<a href="https://agentmods.dev/skills/zakelfassi/skills-driven-development/api-endpoint"><img src="https://agentmods.dev/badge/skills/zakelfassi/skills-driven-development/api-endpoint/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.
<a href="https://agentmods.dev/skills/zakelfassi/skills-driven-development/api-endpoint"><img src="https://agentmods.dev/badge/skills/zakelfassi/skills-driven-development/api-endpoint.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00040 | $0.00590 |
| Opus 5.5 | $0.00016 | $0.00236 |
| Sonnet 5.5 | $0.00008 | $0.00118 |
| Haiku 4.5 | $0.00004 | $0.00059 |
Grade A, and why
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 1mo 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
API Endpoint Scaffold
Create a new REST API endpoint following project conventions.
Inputs
- Entity name (singular, e.g.,
comment) - Fields (name:type pairs, e.g.,
body:string, author_id:number) - Auth required? (boolean, defaults to
true) - Nested under? (optional parent entity, e.g.,
post)
Steps
-
Create the route file
src/routes/{entity}.routes.ts- Define CRUD routes:
GET /,GET /:id,POST /,PUT /:id,DELETE /:id - If nested:
GET /{parent}s/:parentId/{entity}s
- Define CRUD routes:
-
Create the controller
src/controllers/{entity}.controller.ts- One method per route
- All responses use
{ data, error, meta }shape - Handle not-found with 404, validation with 422
-
Create the validation schema
src/validators/{entity}.validator.ts- Use Zod schemas matching the field definitions
- Separate schemas for create vs. update (update = partial)
-
Create the test file
tests/api/{entity}.test.ts- Test each CRUD operation
- Test validation (bad input returns 422)
- Test auth (if required: 401 without token)
- Use test factories for fixtures
-
Register the route
src/routes/index.ts- Add import +
app.use('/{entity}s', {entity}Routes) - If auth required: add auth middleware
- Add import +
Conventions
- Route paths are plural (
/comments, not/comment) - File names are singular (
comment.routes.ts) - All endpoints return
{ data, error, meta } metaincludes pagination for list endpoints- Auth middleware is applied at the route level, not controller level
Edge Cases
- File upload endpoints: Add
multermiddleware, acceptmultipart/form-data - Nested routes: Parent ID is validated in middleware (404 if parent doesn't exist)
- Soft delete:
DELETEsetsdeleted_attimestamp, doesn't remove the row
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.
- 1mo ago First seen · 73 lines · 40 tokens per session scan A 89f8ba6ca487
api-endpoint is a skill published in the GitHub repository zakelfassi/skills-driven-development (18 stars, last pushed 3mo ago), licensed MIT. It adds 40 tokens to every session and 590 once invoked, about $0.0002 per session on Opus 5.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
build-mcp-server
This skill should be used when the user asks to "build an MCP server", "create an MCP", "make an MCP integration", "wrap an API for Claude", "expose tools to Claude", "make an MCP app", or discusses building something with the Model Context Protocol. It is the entry point for MCP server development — it interrogates…
data-manager-api-setup
Guides developers through client library installation and authentication setup steps for the Data Manager API. Use this skill when a user is getting started with the Data Manager API and needs to setup their local environment, install the client library, or setup access to the API. Don't use for implementing audience…
vss-manage-video-io-storage
Use to drive vss vios for sensor list, timelines, clips, snapshots, and add/delete of video or stream sources, and the VIOS REST API only for what that CLI does not cover (sensor info/status/settings, storage and recorder status, WebRTC, the RTSP proxy, network scan, device settings, bytes to disk, the NvStreamer…
vss-search-archive
Use this skill when a user wants to search archived VSS video that is already registered in a configured deployment — by natural-language, similarity, attribute, object-ID, or lexical tag query. Not for fresh clip Q&A, live captioning, video summarization, deployment, or source ingestion/deletion.
workers-best-practices
Cloudflare Workers best practices for production applications. Use when writing, reviewing, or configuring Workers.
new
Create a new project to start development quickly.