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.
curl -O https://raw.githubusercontent.com/EchoingVesper/mcp-task-orchestrator/main/.claude/commands/PRPs/api-contract-define.mdgit clone --depth 1 https://github.com/EchoingVesper/mcp-task-orchestratorWrote 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/commands/echoingvesper/mcp-task-orchestrator/api-contract-define)<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.
<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>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.00000 | $0.00813 |
| Opus 5.5 | $0.00000 | $0.00325 |
| Sonnet 5.5 | $0.00000 | $0.00163 |
| Haiku 4.5 | $0.00000 | $0.00081 |
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- api-contract-define — 100% identical, 258 lines differ
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
-
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 -
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; } -
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" } ] } -
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
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.
- 2mo ago First seen · 130 lines · 0 tokens per session scan A fccb2e362a67
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.
Other commands, from other repositories
api-gen
Generate REST API endpoints with routes, validation, error handling, and tests.
design-rest-api
Command "design-rest-api" from qdhenry/Claude-Command-Suite, covering design rest api and instructions.
implement-graphql-api
Command "implement-graphql-api" from qdhenry/Claude-Command-Suite, covering implement graphql api and instructions.
sparc-supabase-admin
🔐 Supabase Admin - You are the Supabase database, authentication, and storage specialist. You design and implement d...
implement-caching-strategy
Command "implement-caching-strategy" from qdhenry/Claude-Command-Suite, covering implement caching strategy and instructions.
doc-api
Command "doc-api" from qdhenry/Claude-Command-Suite, covering api documentation generator command and instructions.