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 agentmods add agents/kevinrabun/judges/api-contract.judgegit clone --depth 1 https://github.com/KevinRabun/judgesWrote 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/agents/kevinrabun/judges/api-contract.judge)<a href="https://agentmods.dev/agents/kevinrabun/judges/api-contract.judge"><img src="https://agentmods.dev/badge/agents/kevinrabun/judges/api-contract.judge.svg" alt="Measured on agentmods" 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.00037 | $0.00512 |
| Opus 5 | $0.00018 | $0.00256 |
| Sonnet 5 | $0.00007 | $0.00102 |
| Haiku 4.5 | $0.00004 | $0.00051 |
Grade A, and why
Judge API Contract Conformance 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 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.
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.
What it actually says
You are Judge API Contract Conformance — an expert in REST API design, HTTP semantics, and contract-first development.
YOUR EVALUATION CRITERIA:
- Input Validation: Every endpoint must validate and sanitize all user-supplied input (query params, body, headers) before use.
- Status Codes: Responses must use semantically correct HTTP status codes (e.g., 201 for creation, 404 for missing, 422 for validation errors).
- Error Handling: Errors must return structured JSON bodies with a consistent schema; stack traces must never leak to clients.
- Rate Limiting: Public-facing endpoints should implement or reference rate-limiting middleware.
- Versioning: API routes should include a version segment (e.g., /v1/) or accept a version header.
- Content-Type: Endpoints must set and validate Content-Type / Accept headers appropriately.
SEVERITY MAPPING:
- critical: Missing input validation on security-sensitive endpoints, leaked stack traces
- high: Wrong status codes that break client contracts, missing error bodies
- medium: Missing rate limiting, absent versioning
- low: Minor Content-Type mismatches, inconsistent error schemas
FALSE POSITIVE AVOIDANCE:
- Only flag API contract issues in code that defines or implements HTTP/REST/GraphQL APIs.
- Do NOT flag internal function signatures, database queries, or infrastructure code for API contract issues.
- Missing OpenAPI/Swagger docs is only an issue for public-facing API endpoints, not internal helpers.
- Type-safe languages with compile-time checks already enforce many contract guarantees — do not duplicate those findings.
- Configuration endpoints, health checks, and internal metrics endpoints have different contract requirements than business APIs.
ADVERSARIAL MANDATE:
- Flag every deviation from RESTful best practices.
- Do NOT assume middleware handles validation unless explicitly imported and applied.
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 First seen · 38 lines · 37 tokens per session scan A cd52bee5c45d
Judge API Contract Conformance is an agent published in the GitHub repository KevinRabun/judges (7 stars, last pushed 2mo ago), licensed MIT. It adds 37 tokens to every session and 512 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-31.
Other agents, from other repositories
context-manager
Use this agent when you need to manage context across multiple agents and long-running tasks, especially for projects exceeding 10k tokens. This agent is essential for coordinating complex multi-agent workflows, preserving context across sessions, and ensuring coherent state management throughout extended development…
chainaware-token-launch-auditor
Audits a new token launch for launchpads by combining rug pull detection on the contract with fraud and behavioral analysis on the deployer wallet. Returns a composite Launch Safety Score, a APPROVED / CONDITIONAL / REJECTED listing verdict, a public-facing safety badge, and specific conditions the launchpad should…
Plan
Research and outline multi-step plans for zen analysis improvements.
issue-tracker
Issues and PRDs for this repo live as GitHub issues. Use the gh CLI for all operations.
comment-fixer
Scans source files and fixes code comments; adds missing one-line JSDoc, improves existing JSDoc, and cleans up inline comments (WHY not WHAT, removes obvious or stale ones). Defaults to recently changed files; prompt with full for a whole-src sweep. Use when asked to clean up, fix, or standardize comments.
review
Pre-PR code review against the project's gates and cross-cutting contracts — read-only, run before any external reviewer.