Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/event4u-app/agent-confignpx agentmods add skills/event4u-app/agent-config/api-endpointWrote 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/event4u-app/agent-config/api-endpoint)<a href="https://agentmods.dev/skills/event4u-app/agent-config/api-endpoint"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/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/event4u-app/agent-config/api-endpoint"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/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.00043 | $0.01307 |
| Opus 5.5 | $0.00017 | $0.00523 |
| Sonnet 5.5 | $0.00009 | $0.00261 |
| Haiku 4.5 | $0.00004 | $0.00131 |
Grade A, and why
api-endpoint scanned grade A with 1 finding 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 5d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
10. **Verify** — run the project type-checker + targeted tests + smoke probe (`curl` / Bruno / Postman / integration test). How it starts
The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
api-endpoint
Grounded corpus: endpoint-shape decisions (pagination, error shape, idempotency, rate limits) are grounded via the
api-designcorpus —node <skills-root>/corpus-grounding/scripts/ground.mjs search --manifest <skills-root>/api-design/data/manifest.json "<concern>".
When to use
Use this skill when the user asks to create a new API endpoint, REST route, or HTTP handler.
Do NOT use when:
- Modifying existing endpoints — use the code-refactoring skill.
- API design decisions (versioning, deprecation, contract shape) — use
api-design.
Stack routing
Detect the stack, then hand off to the matching carve-out skill for the framework-specific procedure (file layout, validation primitive, response-shaping convention).
| Detected stack | Carve-out skill |
|---|---|
Laravel (artisan + composer.json with laravel/framework) |
laravel-api-endpoint |
Symfony (bin/console + composer.json with symfony/framework-bundle) |
symfony-workflow |
Next.js (next in package.json) |
nextjs-patterns |
| Express / Fastify / NestJS / plain Node | follow project conventions in agents/ + package.json scripts |
| FastAPI / Django / Flask | follow project conventions in agents/ + pyproject.toml |
Go (net/http, gin, echo, fiber) |
follow project conventions in agents/ + go.mod |
Rust (axum, actix-web, rocket) |
follow project conventions in agents/ + Cargo.toml |
If the project doc folder (agents/) has an endpoint-creation guide, that is the source of truth — read it before generating code.
Procedure: Create an API endpoint (stack-neutral)
- Read project docs — Check
./agents/andAGENTS.mdfor endpoint conventions, routing layout, response shape. - Detect stack and route to the carve-out per the table above.
- Plan the endpoint — method, path, request shape, response shape, auth requirement, idempotency.
- Create the route registration in the project's routing surface (route file, decorator-annotated handler, file-based router).
- Create the request handler / controller — thin; delegate business logic to a service / use-case.
- Validate input at the boundary via the framework's validation primitive (FormRequest, Zod, class-validator, Pydantic, struct-tag validators, etc.) — never inline ad-hoc
ifchecks. - Authorize the action via the framework's authz primitive (Policy, voter, guard, middleware, route dependency).
- Shape the response through a transformer / serializer / DTO — never return raw ORM entities.
- Document the endpoint (OpenAPI annotations / generated spec / project doc).
- Verify — run the project type-checker + targeted tests + smoke probe (
curl/ Bruno / Postman / integration test).
What ships with it
1 file 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.
- 5d ago Changed 28b6d6cc3231
- 1mo ago First seen · 102 lines · 43 tokens per session scan A d9b26054feda
api-endpoint is a skill published in the GitHub repository event4u-app/agent-config (12 stars, last pushed yesterday), licensed MIT. It adds 43 tokens to every session and 1,307 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
cqrs-implementation
Implement Command Query Responsibility Segregation for scalable architectures. Use when separating read and write models, optimizing query performance, or building event-sourced systems.
diagnose-backend-bug
Diagnose a bounded backend or multi-service failure from GitHub Issues, Jira, Aone, user-provided exports, logs, traces, responses, stack traces, or job records. Use when a service, API, RPC, worker, queue, CLI, or scheduled job bug needs correlation through the project's existing observability route before repair; do…
api-doc-generator
Generate API documentation from source code, supporting REST APIs, GraphQL, and various documentation formats.
telnyx-ai-inference-curl
Access Telnyx LLM inference APIs, embeddings, and AI analytics for call insights and summaries. This skill provides REST API (curl) examples.
telnyx-ai-assistants-curl
AI voice assistants with custom instructions, knowledge bases, and tool integrations.
telnyx-email-domains-curl
Manage email sending domains, verify DNS records (SPF, DKIM, DMARC, MX), check domain health, and configure domain-level webhooks for delivery events.