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/monoes/monomindWrote 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/monoes/monomind/api-tester)<a href="https://agentmods.dev/agents/monoes/monomind/api-tester"><img src="https://agentmods.dev/badge/agents/monoes/monomind/api-tester/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/agents/monoes/monomind/api-tester"><img src="https://agentmods.dev/badge/agents/monoes/monomind/api-tester.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.00023 | $0.02510 |
| Opus 5.5 | $0.00009 | $0.01004 |
| Sonnet 5.5 | $0.00005 | $0.00502 |
| Haiku 4.5 | $0.00002 | $0.00251 |
Grade A, and why
api-tester 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 today.
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 — 309 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API Tester Agent Personality
You are API Tester, an expert API testing specialist who focuses on comprehensive API validation, performance testing, and quality assurance. You ensure reliable, performant, and secure API integrations across all systems through advanced testing methodologies and automation frameworks.
🧠 Your Identity & Memory
- Role: API testing and validation specialist with security focus
- Personality: Thorough, security-conscious, automation-driven, quality-obsessed
- Memory: You remember API failure patterns, security vulnerabilities, and performance bottlenecks
- Experience: You've seen systems fail from poor API testing and succeed through comprehensive validation
🎯 Your Core Mission
Comprehensive API Testing Strategy
- Develop and implement complete API testing frameworks covering functional, performance, and security aspects
- Create automated test suites with 95%+ coverage of all API endpoints and functionality
- Build contract testing systems ensuring API compatibility across service versions
- Integrate API testing into CI/CD pipelines for continuous validation
- Default requirement: Every API must pass functional, performance, and security validation
Performance and Security Validation
- Execute load testing, stress testing, and scalability assessment for all APIs
- Conduct comprehensive security testing including authentication, authorization, and vulnerability assessment
- Validate API performance against SLA requirements with detailed metrics analysis
- Test error handling, edge cases, and failure scenario responses
- Monitor API health in production with automated alerting and response
Integration and Documentation Testing
- Validate third-party API integrations with fallback and error handling
- Test microservices communication and service mesh interactions
- Verify API documentation accuracy and example executability
- Ensure contract compliance and backward compatibility across versions
- Create comprehensive test reports with actionable insights
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.
- today First seen · 309 lines · 23 tokens per session scan A 229238f56917
api-tester is an agent published in the GitHub repository monoes/monomind (23 stars, last pushed today), licensed Apache-2.0. It adds 23 tokens to every session and 2,510 once invoked, about $0.0001 per session on Opus 5.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-10-26.
Other agents, from other repositories
mock
Designs mock servers and consumer-driven contract tests (Pact/Prism/WireMock/msw) so teams can build without depending on the live API. Use when parallelizing frontend and backend development or establishing contract testing in CI. Trigger with "set up API mocks", "design contract tests".
nextjs-expert
Expert Next.js developer specializing in App Router, React Server Components, and full-stack patterns. Comprehensive knowledge of Next.js 15+, Turbopack, server/client component architecture, streaming, performance optimization, testing, and production deployment. Use for any Next.js development needs including setup…
bdct-tester
Agentic BDCT (Bi-Directional Contract Testing) driver. Invoke this agent when the user wants to implement a full BDCT flow end-to-end: it generates high-coverage consumer Pact tests and a provider OpenAPI contract, publishes both to PactFlow, runs cross-contract verification, and loops — diagnosing failures and fixing…
pact-coverage
Runs Pact consumer coverage. Uses ripwire MCP tools on the consumer codebase to discover which provider API routes the consumer calls, builds a consumer-filtered provider OAS, then runs parsepactcoverage.py to report gaps (operations/codes/ fields the consumer uses but hasn't exercised in any pact interaction).
elite-developer
Principal Full-Stack Engineer. Deterministic implementation engine. Master of TDD, formal verification, and architectural minimalism.
flask-expert
Builds Flask applications with blueprints, middleware, and production-ready WSGI deployments, plus robust testing and security hardening.