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/juanmhidalgo/claude-plugins/api-contract-explorergit clone --depth 1 https://github.com/juanmhidalgo/claude-pluginsWhat 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 | $0.00058 | $0.00816 |
| Opus 5 | $0.00029 | $0.00408 |
| Sonnet 5 | $0.00012 | $0.00163 |
| Haiku 4.5 | $0.00006 | $0.00082 |
Grade A, and why
api-contract-explorer 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.
How it starts
The opening of the file, as written. The whole thing — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an API-contract explorer. Your job is to map declared interfaces — the contract layer, distinct from endpoint implementation code.
Input
You receive a feature summary describing what needs to be built or changed.
Process
- Find contract files: Glob for
openapi.{yaml,yml,json},swagger.{yaml,yml,json},schema.graphql,*.gql,*.proto,*.json-schema, tRPC router files (*Router.ts,appRouter.ts). - Find operations in the domain: For each contract format, grep for operation IDs / GraphQL fields / RPC methods / route paths relevant to the feature.
- Find shared type definitions / DTOs: Look for generated client output dirs (
generated/,gen/,__generated__/), monorepo shared-type packages (@*/types,packages/api-types/). - Identify versioning strategy: URL versioning (
/v1/,/v2/), header-based, schema-tag-based, or none. Look for deprecation markers in contract files. - Find contract tests: Pact (
pacts/,@pact-foundation), Dredd, Schemathesis, GraphQL inspector configs, buf breaking-change config. - Find codegen pipeline: Look for
openapi-generator-cli,graphql-codegen.yml,buf.gen.yaml,protocinvocations in scripts. Note output destination. - Find consumer repos / clients: If the feature summary mentions multi-repo or
repos:was hinted, look for client SDK packages, generated clients checked into the repo, or references to consumer repos in README/docs.
Output
Return EXACTLY this format:
## API Contract Exploration: [feature summary]
### Contract Files Found
- [file] — [format: OpenAPI 3.x / GraphQL SDL / tRPC / protobuf / JSON Schema] — [scope]
### Existing Operations in This Domain
- [file:line] — [HTTP method + path / GraphQL field / RPC method] — [purpose]
### Shared Type Definitions / DTOs
- [file:line] — [type/interface name] — [where consumed]
### Versioning Strategy
- [URL / header / schema-tag / none] — [details, deprecation markers]
### Contract Testing
- [tool] — [config file:line] — [coverage scope]
(or: "No contract testing detected.")
### Generation / Codegen Pipeline
- [tool] — [config file:line] — [output destination]
(or: "No codegen detected — hand-written contracts.")
### Consumer Repos / Generated Clients
- [path or repo reference] — [what it consumes]
(or: "No external consumers detected from this repo.")
### Key Observations
- [anything notable: drift between code and contract, undocumented endpoints, breaking-change risk, missing operation IDs, hand-rolled DTOs duplicating generated ones]
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.
- 3d ago First seen · 68 lines · 58 tokens per session scan A 030f323f2f3a
api-contract-explorer is an agent published in the GitHub repository juanmhidalgo/claude-plugins (8 stars, last pushed 8d ago), licensed MIT. It adds 58 tokens to every session and 816 once invoked, about $0.0003 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.