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/ahmed3elshaer/everything-claude-code-mobileWrote 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/commands/ahmed3elshaer/everything-claude-code-mobile/feature-test)<a href="https://agentmods.dev/commands/ahmed3elshaer/everything-claude-code-mobile/feature-test"><img src="https://agentmods.dev/badge/commands/ahmed3elshaer/everything-claude-code-mobile/feature-test/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/commands/ahmed3elshaer/everything-claude-code-mobile/feature-test"><img src="https://agentmods.dev/badge/commands/ahmed3elshaer/everything-claude-code-mobile/feature-test.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.00389 |
| Opus 5.5 | $0.00012 | $0.00156 |
| Sonnet 5.5 | $0.00006 | $0.00078 |
| Haiku 4.5 | $0.00003 | $0.00039 |
Grade A, and why
feature-test 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.
What it actually says
Feature Test Command
Phase 3 of the feature build pipeline. Creates comprehensive tests for the implemented feature using parallel test-writing agents.
Usage
/feature-test auth
/feature-test offline-cache
/feature-test push-notifications
Prerequisite
Implementation phase must be complete for the feature.
Parallel Execution
Three agents run in parallel, each reading the plan's test strategy section:
unit-test-writer
- ViewModel tests (state transitions, error handling)
- UseCase tests (business logic, edge cases)
- Repository tests (data mapping, caching logic)
- Mapper/DTO tests
ui-test-writer
- Compose/SwiftUI screen tests (rendering, interactions)
- Component tests (states, callbacks)
- Navigation tests (routes, deep links)
- Accessibility tests
mobile-e2e-runner
- End-to-end user flow tests
- Happy path scenarios
- Error path scenarios
- Offline/online transitions
Coverage Targets
| Layer | Target |
|---|---|
| ViewModel / UseCase | 100% |
| Repository | 90% |
| UI Components | 80% |
| E2E Flows | Critical paths |
| Overall minimum | 80% |
Output
Test files created alongside source files following platform conventions:
- Android:
src/test/(unit),src/androidTest/(UI/E2E) - iOS:
Tests/(unit),UITests/(UI/E2E)
Invokes
unit-test-writeragentui-test-writeragentmobile-e2e-runneragent
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 · 64 lines · 31 tokens per session scan A a89a7440287b
feature-test is a command published in the GitHub repository ahmed3elshaer/everything-claude-code-mobile (66 stars, last pushed 4mo ago), licensed MIT. It adds 31 tokens to every session and 389 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-09-03.
Other commands, from other repositories
test-simulator
Launch simulator testing agent for test scenarios and visual verification.
flutter-test
Run Flutter/Dart tests, report failures, and incrementally fix test issues. Covers unit, widget, golden, and integration tests.
ios-test
Bu komut iOS/SwiftUI uygulamasini derleyip simulator'da acarak computer use ile gorsel test yapar.
flutter-test
Run Flutter/Dart tests, report failures, and incrementally fix test issues. Covers unit, widget, golden, and integration tests.
flutter-test
Run Flutter/Dart tests, report failures, and incrementally fix test issues. Covers unit, widget, golden, and integration tests.
checklist
Generate a custom checklist for the current feature based on user requirements.