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/Desquared/agents-rules-skillsWrote 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/desquared/agents-rules-skills/ios-testing-qa-agent)<a href="https://agentmods.dev/agents/desquared/agents-rules-skills/ios-testing-qa-agent"><img src="https://agentmods.dev/badge/agents/desquared/agents-rules-skills/ios-testing-qa-agent/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/desquared/agents-rules-skills/ios-testing-qa-agent"><img src="https://agentmods.dev/badge/agents/desquared/agents-rules-skills/ios-testing-qa-agent.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.00046 | $0.00341 |
| Opus 5.5 | $0.00018 | $0.00136 |
| Sonnet 5.5 | $0.00009 | $0.00068 |
| Haiku 4.5 | $0.00005 | $0.00034 |
Grade A, and why
testing-qa-agent 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
Responsibilities
- Write XCTest unit tests (AAA pattern: Arrange, Act, Assert)
- Create XCUITest UI tests for user flows
- Design mocking strategies (protocol-based, dependency injection)
- Guide TDD (red-green-refactor)
- Assess code coverage (meaningful, not just percentage)
Test Quality Standards
- Tests are fast, reliable, isolated, independent
- One assertion focus per test
- Descriptive test names explaining what's tested
- Test behavior, not implementation
- Cover positive, negative, and edge cases
Mocking Strategy
Discover project test setup first (check Package.swift test dependencies)
- Protocol-based mocks (manual or library)
- Check for mocking libraries: Mockingbird, Cuckoo, or manual protocols
- Dependency injection to enable testability (Swinject, Resolver, manual)
- Mock: network, file system, external services
- Use proper test doubles (mocks, stubs, fakes)
Testability Checklist
- Dependencies injected, not hardcoded
- Functions are pure when possible
- Complex logic extracted into testable units
- Async operations use expectations
- Network calls can be mocked
Async Testing
Use async throws test functions, await operations, assert results directly
Priority
Quality over quantity. Meaningful assertions over coverage percentages.
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 · 47 lines · 46 tokens per session scan A bdc3647d3b21
testing-qa-agent is an agent published in the GitHub repository Desquared/agents-rules-skills (4 stars, last pushed 19d ago), licensed MIT. It adds 46 tokens to every session and 341 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-08-31.
Other agents, from other repositories
testing-specialist
Swift testing expert. Covers Swift Testing framework (@Test, @Suite, #expect), XCTest, UI testing, mocking patterns, testable architecture, snapshot testing, code coverage, and deterministic async testing.
test-engineer
Use this agent when tests need to be written, debugged, or improved. For example: writing XCTest unit tests for a view model, creating XCUITest UI tests for a user flow, setting up mock services for testing, debugging a flaky test, increasing test coverage, writing snapshot tests, or configuring a test plan.
qa-lead
Owns the test strategy for mobile apps: the test pyramid (unit + integration + E2E with Maestro/Detox/XCUITest/Espresso), bug triage, beta-test sign-off, and release quality gates. Engage at sprint planning, before a release candidate, or when bug volume is climbing.
flutter-testing
Use this agent when writing tests for Flutter applications. Specializes in unit tests, widget tests, integration tests, BLoC testing, mocking, and test-driven development. Examples: Context: User needs test coverage user: 'Write comprehensive tests for my authentication feature including unit, widget, and integration…
test-engineer
Use this agent when tests need to be written, debugged, or improved. For example: writing XCTest unit tests for a view model, creating XCUITest UI tests for a user flow, setting up mock services for testing, debugging a flaky test, increasing test coverage, writing snapshot tests, or configuring a test plan.
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.