api-designer

A helper for designing and documenting REST APIs with OpenAPI or Swagger specifications. REST APIs let software exchange data through web requests, while OpenAPI describes those requests and responses in a standard format.

In plain words
What is it for?
Use it to plan operations such as creating, reading, updating, and deleting resources, define request and response JSON structures, and produce OpenAPI 3.0 or newer specifications.
Why use it?
It helps turn requirements into clearly named endpoints, data schemas, authentication rules, and usable API documentation.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/aidotnet/moyucode/api-designer
Any agent
npx skills add AIDotNet/MoYuCode --skill api-designer
Clone the repo
git clone --depth 1 https://github.com/AIDotNet/MoYuCode

Made for: Claude Code, Codex.

Per session 39 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 791 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00039 $0.00791
Opus 5 $0.00019 $0.00396
Sonnet 5 $0.00008 $0.00158
Haiku 4.5 $0.00004 $0.00079

Measured 3d ago against content hash 8f25eae4f62b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

api-designer 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 3d 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.

skills/community/api-designer/SKILL.md · 111 lines

How it starts

The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.

API Designer Skill

Description

Design and document RESTful APIs with OpenAPI/Swagger specifications following industry best practices.

Trigger

  • /api-design command
  • User requests API design or documentation
  • User needs OpenAPI/Swagger specification

Prompt

You are an API design expert that creates well-structured RESTful APIs. Your goal is to:

  1. Design Endpoints: Create RESTful endpoints following naming conventions
  2. Define Schemas: Create request/response JSON schemas
  3. Generate OpenAPI: Produce OpenAPI 3.0+ specifications
  4. Document: Provide comprehensive API documentation

Instructions

When designing an API:

  1. Analyze Requirements:

    • What resources need to be exposed?
    • What operations are needed (CRUD, custom actions)?
    • What authentication is required?
    • What are the data relationships?
  2. Design Endpoints:

    GET    /api/v1/users          # List users
    POST   /api/v1/users          # Create user
    GET    /api/v1/users/{id}     # Get user by ID
    PUT    /api/v1/users/{id}     # Update user
    DELETE /api/v1/users/{id}     # Delete user
    
  3. Define Request/Response Schemas:

    {
      "type": "object",
      "properties": {
        "id": { "type": "string", "format": "uuid" },
        "name": { "type": "string", "minLength": 1 },
        "email": { "type": "string", "format": "email" },
        "createdAt": { "type": "string", "format": "date-time" }
      },
      "required": ["name", "email"]
    }
    
  4. Generate OpenAPI Specification:

    openapi: 3.0.3
    info:
      title: User API
      version: 1.0.0
    paths:
      /users:
        get:
          summary: List all users
          responses:
            '200':
              description: Successful response
              content:
                application/json:
                  schema:
                    type: array
                    items:
                      $ref: '#/components/schemas/User'
    

Design Principles

Read the full file on GitHub · 111 lines

Changes

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.

  1. 3d ago First seen · 111 lines · 39 tokens per session scan A 8f25eae4f62b

Subscribe to this mod's changes

api-designer is a skill published in the GitHub repository AIDotNet/MoYuCode (84 stars, last pushed 7mo ago), licensed MIT. It adds 39 tokens to every session and 791 once invoked, about $0.0002 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-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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.

obra/superpowers · 37 tokens

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.

microsoft/vscode · 62 tokens

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.

microsoft/vscode · 51 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens