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/CarolaneLFBV/ios-development-agentsWrote 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/carolanelfbv/ios-development-agents/test)<a href="https://agentmods.dev/commands/carolanelfbv/ios-development-agents/test"><img src="https://agentmods.dev/badge/commands/carolanelfbv/ios-development-agents/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/carolanelfbv/ios-development-agents/test"><img src="https://agentmods.dev/badge/commands/carolanelfbv/ios-development-agents/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.00016 | $0.00258 |
| Opus 5.5 | $0.00006 | $0.00103 |
| Sonnet 5.5 | $0.00003 | $0.00052 |
| Haiku 4.5 | $0.00002 | $0.00026 |
Grade A, and why
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 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.
What it actually says
/ios:test
Generate or run the tests requested in $ARGUMENTS using testing specialist
expertise. Work directly unless delegation is explicitly requested.
--type unit|ui|snapshot|performance|allselects tests (default: unit).--coveragecollects and reports coverage with available project tooling.--generateadds meaningful regression tests for existing behavior.--fixrepairs demonstrated failures within scope, preserving intended behavior.
Inspect target/toolchain compatibility and existing suites. Use Swift Testing for suitable new unit tests; preserve XCTest, and use XCTest/XCUITest for UI/performance. Check the target's testing requirements and existing snapshot solution before adding dependencies.
Keep fixtures isolated and async synchronization deterministic. Never start a Task
and immediately assume its loading-state mutation ran. Discover actual schemes,
test plans and installed simulators; use swift test for compatible packages.
Run relevant tests when possible. Report exact commands, passed/failed/skipped results, measured coverage and blockers. Generated tests are not automatically passed tests.
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 · -45 lines · +6 tokens per session 1140c913a089
- 1mo ago First seen · 72 lines · 10 tokens per session scan A 80b494c6099e
test is a command published in the GitHub repository CarolaneLFBV/ios-development-agents (7 stars, last pushed yesterday), licensed MIT. It adds 16 tokens to every session and 258 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-31.
Other commands, from other repositories
generate-widget
Génération Widget Flutter avec Tests.
create-widget
Create a Flutter widget with proper state management and Material/Cupertino design.
flutter-test
Run Flutter/Dart tests, report failures, and incrementally fix test issues. Covers unit, widget, golden, and integration tests.
feature-test
Create all tests for an implemented feature - unit tests (ViewModel, UseCase, Repository), Compose UI tests, and E2E user flow tests.
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.