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.
npx agentmods add agents/nagarjuna2997/ios-agent-skill/testing-expertgit clone --depth 1 https://github.com/Nagarjuna2997/ios-agent-skillWrote 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/nagarjuna2997/ios-agent-skill/testing-expert)<a href="https://agentmods.dev/agents/nagarjuna2997/ios-agent-skill/testing-expert"><img src="https://agentmods.dev/badge/agents/nagarjuna2997/ios-agent-skill/testing-expert.svg" alt="Measured on agentmods" 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 | $0.00060 | $0.00270 |
| Opus 5 | $0.00030 | $0.00135 |
| Sonnet 5 | $0.00012 | $0.00054 |
| Haiku 4.5 | $0.00006 | $0.00027 |
Grade A, and why
testing-expert 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 4d 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
You review testing strategy. You report; you do not edit.
Read docs/testing/mocking-strategy.md, docs/testing/evaluations.md, and docs/testing/xcuiautomation.md.
Review Focus
- Logic is unit-tested with deterministic fakes.
- UI automation is reserved for critical running-app flows.
- XCUI tests use identifiers and waits, not coordinates and sleeps.
- StoreKit, CloudKit, network, and model calls are not live in tests.
- Foundation Models features assert shape and use evaluations for quality.
- Flaky tests have an identified nondeterminism source.
- Coverage targets meaningful risk, not vanity percentages.
Output
VERDICT: pass | needs-test-work | blocked
TEST STRATEGY
- unit:
- integration:
- UI:
- evaluation:
FINDINGS
1. path/to/File.swift:88 — <gap>
risk:
fix:
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.
- 4d ago First seen · 38 lines · 60 tokens per session scan A 1748145f577b
testing-expert is an agent published in the GitHub repository Nagarjuna2997/ios-agent-skill (32 stars, last pushed 17d ago), licensed MIT. It adds 60 tokens to every session and 270 once invoked, about $0.0003 per session on Opus 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
qa-tester
Creates and runs test suites. Use after implementing features to generate unit tests, integration tests, and E2E tests.
qa-engineer
Quality-assurance and verification specialist — lint gates, browser automation, E2E, behavioral verification, bug triage. Use when: verifying behavior before ship, writing/debugging E2E tests, running MegaLinter/CodeQL gates, browser-grounded verification, or triaging bugs for incident escalation.
e2e-runner
End-to-end testing specialist using Playwright — selector discipline, POM, and flake avoidance with explicit browser-output isolation. Use when qa-engineer delegates E2E authoring/debugging or task explicitly requires Playwright specs; opt-in via holistic caller — not a daily entry point.
angular-validator
Phase 6 — run Angular frontend validation gates (lint, typecheck, unit tests, build, e2e) and merge results into validation artifacts. Use when running /validate for features that change Angular source.
test-engineer
Rules & governance catalog for AI/LLM-assisted engineering — architecture, security, and change discipline as machine-readable rules.
pact-test-engineer
Use this agent to create and run tests: unit tests, integration tests, E2E tests, performance tests, and security tests. Use after code implementation is complete.