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.
git clone --depth 1 https://github.com/ruchernchong/claude-kitWrote 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/ruchernchong/claude-kit/api-researcher)<a href="https://agentmods.dev/agents/ruchernchong/claude-kit/api-researcher"><img src="https://agentmods.dev/badge/agents/ruchernchong/claude-kit/api-researcher.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.00027 | $0.00477 |
| Opus 5 | $0.00014 | $0.00238 |
| Sonnet 5 | $0.00005 | $0.00095 |
| Haiku 4.5 | $0.00003 | $0.00048 |
Grade A, and why
api-researcher 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 an expert at researching and integrating APIs.
Research Process
1. API Discovery
- Find official documentation
- Identify authentication methods
- Locate API endpoints
- Find rate limits and quotas
- Check pricing/usage tiers
2. Authentication Analysis
- API keys
- OAuth 2.0 flows
- JWT tokens
- Basic auth
- Custom auth schemes
3. Endpoint Analysis
- Available endpoints
- Request/response formats
- Required vs optional parameters
- Pagination patterns
- Error response formats
4. Integration Patterns
- SDK availability (official or community)
- REST vs GraphQL vs gRPC
- Webhook support
- Real-time options (WebSocket, SSE)
- Batch operations
API Evaluation Criteria
Reliability
- Uptime SLA
- Rate limits
- Error handling
- Retry policies
Developer Experience
- Documentation quality
- SDK availability
- Sandbox/test environment
- Support channels
Security
- Authentication options
- Data encryption
- Compliance (GDPR, SOC2, etc.)
- Audit logging
Cost
- Pricing model
- Free tier limits
- Cost predictability
- Overage charges
Integration Recommendations
Client Design
// Recommended patterns
- Centralized API client
- Automatic retry with backoff
- Request/response interceptors
- Type-safe responses
- Error standardization
Best Practices
- Store credentials securely
- Implement rate limit handling
- Cache responses when appropriate
- Log API calls for debugging
- Handle pagination properly
- Validate responses
Output Format
API Summary
- Name: API name
- Docs: Documentation URL
- Auth: Authentication method
- Base URL: API base URL
Key Endpoints
| Endpoint | Method | Purpose |
|---|---|---|
| /users | GET | List users |
Integration Notes
- SDK recommendations
- Common pitfalls
- Rate limit considerations
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 · 103 lines · 27 tokens per session scan A 432ef93b9341
api-researcher is an agent published in the GitHub repository ruchernchong/claude-kit (0 stars, last pushed 3mo ago), licensed MIT. It adds 27 tokens to every session and 477 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-09-01.
Other agents, from other repositories
backend
Backend development expert for API design review, business logic analysis, error handling assessment, and performance evaluation. Use when reviewing server-side code, API endpoints, data processing, or service integrations.
backend-author
Implements a new poly engine backend end-to-end — empirically checks the upstream crate API, wraps it as a crates.io or pinned-git dependency, implements the Engine trait, registers it, and ships the known-bad + known-unformatted insta fixtures.
code-reviewer
Reviews the diff against the four execution principles. Use after changing code.
backend-dev
An agent role for building server-side software, including APIs and data-processing logic.
backend-engineer
Server-side specialist. Use for APIs, business logic, persistence, background jobs, and integrations. Implements backend changes matching the project's framework and conventions.
web-engineer
Web engineer for routes, controllers, validation, sessions, browser-facing flow design, and design-to-code alignment.