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 EliasOulkadi/shokunin --skill api-forgegit clone --depth 1 https://github.com/EliasOulkadi/shokuninWrote 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/eliasoulkadi/shokunin/api-forge)<a href="https://agentmods.dev/skills/eliasoulkadi/shokunin/api-forge"><img src="https://agentmods.dev/badge/skills/eliasoulkadi/shokunin/api-forge/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/eliasoulkadi/shokunin/api-forge"><img src="https://agentmods.dev/badge/skills/eliasoulkadi/shokunin/api-forge.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00085 | $0.03039 |
| Opus 5.5 | $0.00034 | $0.01216 |
| Sonnet 5.5 | $0.00017 | $0.00608 |
| Haiku 4.5 | $0.00009 | $0.00304 |
Grade A, and why
api-forge 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.
How it starts
The opening of the file, as written. The whole thing — 359 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API Forge
Design APIs that developers love. Based on patterns from Stripe, GitHub, Twilio, Slack, and the OpenAPI 3.1 specification.
Sub-Commands
| Command | Category | Description |
|---|---|---|
design |
Build | Design an API from user requirements. Generate OpenAPI 3.1 spec. |
endpoint |
Build | Design a single endpoint with all methods, parameters, responses, and error codes. |
audit |
Evaluate | Audit an existing API against design rules, security checklist, and anti-patterns. |
document |
Document | Generate API documentation from OpenAPI spec or route handlers. |
extract |
Document | Extract OpenAPI spec from existing route handlers. |
webhook |
Build | Design webhook delivery, retry, and signature verification. |
Workflow
Step 1: Determine API type
| Type | Use Case | Spec |
|---|---|---|
| REST | CRUD, resource-oriented | OpenAPI 3.1 |
| GraphQL | Complex queries, multiple resources | Schema Definition Language |
| Webhook | Event-driven, async notifications | Standard webhooks (Stripe pattern) |
Step 2: Define resources and naming
| Pattern | Example | Notes |
|---|---|---|
| Nouns, plural | /users, /orders |
Never verbs |
| Nested (max 2 levels) | /users/{id}/orders |
Flat preferred over deep nesting |
| Actions as sub-resources | /orders/{id}/cancel |
Only for non-CRUD operations |
| Query for filters | /users?role=admin |
Not /users/admins |
| kebab-case for paths | /order-items |
Not /orderItems |
| snake_case for fields | first_name |
Not firstName in JSON:API |
Step 3: Map HTTP methods
| Method | Purpose | Idempotent | Safe | Body |
|---|---|---|---|---|
| GET | Read resource | Yes | Yes | No |
| POST | Create resource | No | No | Yes |
| PUT | Full replace | Yes | No | Yes |
| PATCH | Partial update | No | No | Yes |
| DELETE | Remove resource | Yes | No | Optional |
Step 4: Design response format
Stripe-style standard envelope:
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 · 359 lines · 85 tokens per session scan A 593dba7d9a13
api-forge is a skill published in the GitHub repository EliasOulkadi/shokunin (112 stars, last pushed 19d ago), licensed MIT. It adds 85 tokens to every session and 3,039 once invoked, about $0.0003 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
vector-backend-operations
Select and connect the right vector-store backend for the vector-mcp MCP server — chromadb, postgres/pgvector, qdrant, couchbase, or mongodb — and supply the correct dbtype/connection parameters that every collection and search call needs. Use when the agent must decide which engine to target, wire up…
n8n-subworkflows
Build reusable, composable n8n sub-workflows. Use when extracting shared logic, building anything multi-step or reused across workflows, or any workflow over 10 nodes — and whenever the user mentions sub-workflows, Execute Workflow, reuse, shared/common logic, modular workflows, "Define Below" inputs…
n8n-code-tool
Write JavaScript or Python for the n8n Custom Code Tool (@n8n/n8n-nodes-langchain.toolCode) — the AI-agent-callable tool, NOT the workflow Code node. Use when building a Code Tool attached to an AI Agent, writing code that an LLM will invoke, parsing the query input, returning a string result, defining an input schema…
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.