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/akaszubski/autonomous-devWrote 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/akaszubski/autonomous-dev/mobile-tester)<a href="https://agentmods.dev/agents/akaszubski/autonomous-dev/mobile-tester"><img src="https://agentmods.dev/badge/agents/akaszubski/autonomous-dev/mobile-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/akaszubski/autonomous-dev/mobile-tester"><img src="https://agentmods.dev/badge/agents/akaszubski/autonomous-dev/mobile-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.00031 | $0.01843 |
| Opus 5.5 | $0.00012 | $0.00737 |
| Sonnet 5.5 | $0.00006 | $0.00369 |
| Haiku 4.5 | $0.00003 | $0.00184 |
Grade A, and why
mobile-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 1mo 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 1mo ago First seen · 203 lines · 31 tokens per session scan A 466073c9f4ff
mobile-tester is an agent published in the GitHub repository akaszubski/autonomous-dev (34 stars, last pushed 21d ago), with no licence file. It adds 31 tokens to every session and 1,843 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-08-30.
Other agents, from other repositories
integration-test-reviewer
Reviews changed integration and E2E tests against skeletons, proof obligations, or explicit prompt claims. Use after test implementation or when test review/skeleton verification is requested. Returns only material proof gaps with the smallest sufficient corrections.
acceptance-test-generator
Generates integration/E2E test skeletons from Design Doc ACs using required proof boundaries and existing coverage. Use when Design Doc is complete and test design is needed, or when "test skeleton/AC/acceptance criteria" is mentioned. Behavior-first approach for minimal tests with maximum coverage.
android-emulator-tester
Automated Android UI/integration testing specialist; the agent that drives a real Android app on a headless emulator under WSL/Linux and gates on what it observes. Use when the task is "run the app on an emulator", "smoke-test a screen", "drive the Android UI", "reproduce a tap-and-crash / ANR", "automate an Android…
builder
STRONGLY PREFER to delegate Apple platform builds, tests, and device operations to this agent to preserve your context window. This agent absorbs verbose build logs and returns only success/failure with the relevant error if any. Use for: verifying code compiles, running tests, checking builds aren't broken, managing…
specwright-integration-tester
Integration test engineer for non-unit tiers. Writes integration tests, contract tests, and end-to-end tests that exercise real infrastructure at component boundaries. Never writes skip conditions for missing infrastructure.
frontend-verifier
Verifies frontend via browser automation — forms, interactions, visual regressions, responsive layouts. Also fixes issues found. General frontend QA when there's no Figma involved. Only non-Figma design agent. Good for catching functional bugs (broken forms, console errors) alongside visual issues.