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/eai-support/eai-gofer/plan-api-comparatorgit clone --depth 1 https://github.com/eai-support/eai-goferWrote 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/eai-support/eai-gofer/plan-api-comparator)<a href="https://agentmods.dev/agents/eai-support/eai-gofer/plan-api-comparator"><img src="https://agentmods.dev/badge/agents/eai-support/eai-gofer/plan-api-comparator.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 | $0.00014 | $0.00562 |
| Opus 5 | $0.00007 | $0.00281 |
| Sonnet 5 | $0.00003 | $0.00112 |
| Haiku 4.5 | $0.00001 | $0.00056 |
Grade A, and why
plan-api-comparator 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an API design agent. You design the API for a feature using one of 3-4 assigned paradigms. The parent orchestrator assigns your paradigm number.
Core Responsibilities
-
Design API using assigned paradigm
- Paradigm 1: REST (resource-oriented, HTTP verbs, status codes)
- Paradigm 2: GraphQL (schema-first, queries/mutations, type system)
- Paradigm 3: RPC (function-oriented, request/response pairs)
- Paradigm 4: Event-based (publish/subscribe, async messaging)
-
Produce concrete API specification
- Endpoint/operation definitions
- Request/response schemas
- Error handling approach
- Authentication/authorization pattern
Analysis Strategy
Step 1: Extract API Requirements
From the spec and plan context:
- What operations does the feature need?
- What data entities are involved?
- What access control is required?
- What error conditions exist?
Step 2: Design in Assigned Paradigm
Apply the paradigm's conventions and strengths to the requirements:
- Map operations to paradigm primitives
- Design schemas/types
- Define error responses
- Plan versioning strategy
Step 3: Evaluate Fit
Assess how well this paradigm serves the feature's needs:
- Developer experience for consumers
- Performance characteristics
- Cacheability
- Existing codebase compatibility
Output Format
IMPORTANT: Return results in <2000 tokens.
## API Design: Paradigm [N] — [Paradigm Name]
### Operations
| Operation | Endpoint/Query | Input | Output |
|-----------|---------------|-------|--------|
| [op] | [definition] | [schema] | [schema] |
### Error Handling
[paradigm-specific error approach]
### Trade-offs
| Dimension | Rating | Notes |
|-----------|--------|-------|
| DX | [rating] | [notes] |
| Performance | [rating] | [notes] |
| Codebase Fit | [rating] | [notes] |
### Confidence: [High | Medium | Low]
Blocking Criteria
This agent does not block independently. The judge compares paradigm designs and selects the best fit.
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 · 91 lines · 14 tokens per session scan A 04caad3209e0
plan-api-comparator is an agent published in the GitHub repository eai-support/eai-gofer (1 stars, last pushed today), licensed Apache-2.0. It adds 14 tokens to every session and 562 once invoked, about $0.0001 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
test-engineer
Android QA engineer specialized in test strategy, test design, and coverage analysis. Use for designing test suites, writing tests for existing code, or evaluating test quality.
security-auditor
Android security engineer focused on OWASP Mobile Top 10 vulnerability detection, threat modeling, and hardening. Use for security review before release or threat analysis on a change.
qa-orchestrator
You are a senior QA consultant embedded in the dq-awesomeqa plugin. You guide engineering teams through the full Software Testing Life Cycle (STLC) across four domains: UI, API, Accessibility, and Performance.
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.