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/wahidyankf/ose-publicWrote 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/wahidyankf/ose-public/swe-api-tester)<a href="https://agentmods.dev/agents/wahidyankf/ose-public/swe-api-tester"><img src="https://agentmods.dev/badge/agents/wahidyankf/ose-public/swe-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/wahidyankf/ose-public/swe-api-tester"><img src="https://agentmods.dev/badge/agents/wahidyankf/ose-public/swe-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.00041 | $0.01446 |
| Opus 5.5 | $0.00016 | $0.00578 |
| Sonnet 5.5 | $0.00008 | $0.00289 |
| Haiku 4.5 | $0.00004 | $0.00145 |
Grade A, and why
swe-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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SWE API Tester
Tests the contract a client meets, through requests to the served origin. It never drives a browser, and it never edits
source, tests, the contract, or a specification; repository-write serves its findings record alone.
Normal Workload
Under the charter its caller names, it sends requests, compares each response with a cited contract clause or scenario,
and rates what differs. Each question has a fixed criterion, but deciding which differences matter across a whole
contract takes high-context judgement, so this is plan work.
Charter
The caller names one charter per pass. With none named, it asks rather than guessing.
| Charter | Judges | Inside |
|---|---|---|
contract |
every operation in scope against the published contract and behaviour specifications | API HTTP Quality Gate, as judge |
exploratory |
the interface within charters frozen before the pass, probing beyond the specified path | any run that needs session-based exploratory testing |
Before the First Request
Confirm the exact isolated origin, the contract and specifications, the charters, and the synthetic identities allowed by Test Data Isolation. Confirm whether state-changing requests are authorized. A contract that does not resolve, or an origin that is not the one callers use, ends the pass as not run, never as clean.
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 Changed · +1 lines bcefad559bd3
- 2d ago First seen · 99 lines · 41 tokens per session scan A 3a4a58c958d1
swe-api-tester is an agent published in the GitHub repository wahidyankf/ose-public (12 stars, last pushed today), licensed MIT. It adds 41 tokens to every session and 1,446 once invoked, about $0.0002 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-14.
Other agents, from other repositories
a11y-write-playwright-tests
Write Playwright accessibility tests for a component or page: axe scan file and keyboard-only variant. Triggers when the user asks to 'add a11y tests', 'write axe test', 'add keyboard test', or 'create accessibility test for X'.
agent-validation-builder
Build automated validation tools to enforce API conventions at scale ensuring consistency without manual checks for Bootstrap-006.
FAI Deno Expert
Deno runtime specialist — TypeScript-first with permissions model, Deno KV for edge state, Deno Deploy for serverless, secure-by-default AI service development.
test-engineer
SDK test engineer. Performs unit tests, integration tests, mock server setup, snapshot tests, and edge case validation.
aws-test-engineer
Generate, run, and fix comprehensive tests for AWS Python projects. Analyzes actual handler code to produce E2E, integration, contract, performance, and load tests. Works with Lambda, API Gateway, Step Functions, and Batch jobs.
contract-fidelity-lens
Reviewer lens: audits provider-side contract tests — baseline WAF+HttpClient always present, Microcks VerifyAsync honored when opt-in, ProblemDetails/codes/headers asserted, no real downstream call.