mcp-task-orchestrator: Command for Claude Code

.claude/commands/PRPs/api-contract-define.md

api-contract-define is a command for Claude Code from EchoingVesper/mcp-task-orchestrator. It costs 0 tokens per session (813 once invoked), scanned A, original, MIT.

An API-contract command that documents how a backend and frontend exchange data through REST endpoints, which are web addresses used for reading, creating, updating, and deleting resources.

In plain words
What is it for?
Use it to define list, detail, create, update, and delete endpoints for a feature, along with request and response types and pagination details.
Why use it?
It gives both sides a shared definition of URLs, parameters, request data, response data, status codes, and validation rules.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

This is EchoingVesper/mcp-task-orchestrator's own configuration. It tells Claude Code how to work on mcp-task-orchestrator itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything mcp-task-orchestrator configures →

Reuse

Borrowing it

Nothing to install: this file belongs to EchoingVesper/mcp-task-orchestrator. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/EchoingVesper/mcp-task-orchestrator/main/.claude/commands/PRPs/api-contract-define.md
Clone the repo
git clone --depth 1 https://github.com/EchoingVesper/mcp-task-orchestrator

Made for: Claude Code.

Wrote 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.

agentmods badge for api-contract-define

README.md
[![agentmods](https://agentmods.dev/badge/commands/echoingvesper/mcp-task-orchestrator/api-contract-define/github.svg)](https://agentmods.dev/commands/echoingvesper/mcp-task-orchestrator/api-contract-define)
Your own site
<a href="https://agentmods.dev/commands/echoingvesper/mcp-task-orchestrator/api-contract-define"><img src="https://agentmods.dev/badge/commands/echoingvesper/mcp-task-orchestrator/api-contract-define/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.

agentmods 80×15 button for api-contract-define

Your own site · 80×15
<a href="https://agentmods.dev/commands/echoingvesper/mcp-task-orchestrator/api-contract-define"><img src="https://agentmods.dev/badge/commands/echoingvesper/mcp-task-orchestrator/api-contract-define.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 813 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00000 $0.00813
Opus 5.5 $0.00000 $0.00325
Sonnet 5.5 $0.00000 $0.00163
Haiku 4.5 $0.00000 $0.00081

Measured 2mo ago against content hash fccb2e362a67, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

api-contract-define 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 2mo 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.claude/commands/PRPs/api-contract-define.md · 130 lines

How it starts

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

Define API Contract Between Backend and Frontend

Feature: $ARGUMENTS

Task: Create detailed API contract specification for backend/frontend coordination

  1. Define RESTful endpoints:

    Base URL: /api/v1/{feature}
    
    Endpoints:
    - GET /api/v1/{features}
      Query params: page, size, sort, filter
      Response: Page<{Feature}Response>
    
    - GET /api/v1/{features}/{id}
      Path param: id (Long)
      Response: {Feature}Response
    
    - POST /api/v1/{features}
      Body: {Feature}Request
      Response: {Feature}Response (201 Created)
    
    - PUT /api/v1/{features}/{id}
      Path param: id (Long)
      Body: {Feature}Request
      Response: {Feature}Response
    
    - DELETE /api/v1/{features}/{id}
      Path param: id (Long)
      Response: 204 No Content
    
  2. Define request/response DTOs:

    // Request DTO (for POST/PUT)
    interface {Feature}Request {
      name: string;        // min: 2, max: 100
      description?: string; // max: 1000
      // Add domain-specific fields
    }
    
    // Response DTO (for GET)
    interface {Feature}Response {
      id: number;
      name: string;
      description?: string;
      createdAt: string;   // ISO 8601
      updatedAt: string;   // ISO 8601
      // Add computed fields
    }
    
    // Page response wrapper
    interface Page<T> {
      content: T[];
      totalElements: number;
      totalPages: number;
      size: number;
      number: number;
    }
    
  3. Define error responses:

    {
      "timestamp": "2024-01-20T10:30:00Z",
      "status": 400,
      "error": "Bad Request",
      "message": "Validation failed",
      "path": "/api/v1/{features}",
      "errors": [
        {
          "field": "name",
          "message": "Name is required"
        }
      ]
    }
    
  4. Define validation rules:

    • Backend: Bean Validation annotations
    • Frontend: Matching Zod schemas
    name: required, 2-100 chars
    description: optional, max 1000 chars
    email: valid email format
    date: ISO 8601 format
    

Read the full file on GitHub · 130 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. 2mo ago First seen · 130 lines · 0 tokens per session scan A fccb2e362a67

Subscribe to this mod's changes

api-contract-define is a command published in the GitHub repository EchoingVesper/mcp-task-orchestrator (28 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 813 tokens. 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.