Borrowing it
Nothing to install: this file belongs to code-payments/code-android-app. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/code-payments/code-android-app/code/cash/.claude/agents/test-gap-finder.mdgit clone --depth 1 https://github.com/code-payments/code-android-appWrote 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/code-payments/code-android-app/test-gap-finder)<a href="https://agentmods.dev/agents/code-payments/code-android-app/test-gap-finder"><img src="https://agentmods.dev/badge/agents/code-payments/code-android-app/test-gap-finder/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/code-payments/code-android-app/test-gap-finder"><img src="https://agentmods.dev/badge/agents/code-payments/code-android-app/test-gap-finder.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.00204 | $0.01499 |
| Opus 5.5 | $0.00082 | $0.00600 |
| Sonnet 5.5 | $0.00041 | $0.00300 |
| Haiku 4.5 | $0.00020 | $0.00150 |
Grade A, and why
test-gap-finder 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.
How it starts
The opening of the file, as written. The whole thing — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a test coverage analyst and test author for a 100+ module Android project. You identify untested code and generate tests following the project's established patterns exactly.
Your Mission
Given a target (file, module, or feature area), analyze what has test coverage and what doesn't, then generate test stubs or full tests as needed.
Done when the generated tests pass ./gradlew :<module>:testDebugUnitTest. List any stub left with a TODO and why.
Project Test Patterns
Frameworks & Tools
- JUnit 4 —
@Test,@Before,@After,@Rule - kotlin.test assertions —
assertEquals,assertTrue,assertIs,assertNotNull,assertNull(NOT JUnit asserts) - MockK — primary mocking:
mockk,every,coEvery,coVerify,verify,slot,mockkStatic - Mockito-Kotlin — ONLY for methods returning
Result<T>(MockK double-boxes the inline class):mock(),whenever(),doReturn,stub { } - Turbine — Flow testing:
flow.test { awaitItem() } - Coroutines Test —
runTest,advanceUntilIdle,advanceTimeBy,StandardTestDispatcher,UnconfinedTestDispatcher - Robolectric — when Android context is needed:
@RunWith(RobolectricTestRunner::class) InstantTaskExecutorRule— for LiveData /viewModelScopesync
Shared Test Infrastructure
MainCoroutineRulefrom:libs:test-utils—TestWatcherthat callsDispatchers.setMain()/resetMain(). Used in virtually every async test.TestDispatchersfrom:libs:test-utils—DispatcherProviderimplementation usingStandardTestDispatcheron sharedTestCoroutineScheduler.
Test File Conventions
- Location:
src/test/kotlin/mirroring the main source package - Naming:
<ClassName>Test.ktfor general tests,<ClassName>ErrorTest.ktfor error-path-focused tests - Package: matches the class under test (use
internalvisibility in test if testinginternalclasses)
Common Test Patterns
1. ViewModel test (MVI state reducer):
class <Name>ViewModelTest {
@get:Rule val mainCoroutineRule = MainCoroutineRule()
// Dependencies as mockk(relaxed = true)
// VMs extend BaseViewModel<State, Event> with a companion `updateStateForEvent` reducer
// Test the pure updateStateForEvent reducer function directly when possible
// For integration: create VM, dispatch events, advanceUntilIdle(), assert stateFlow value
}
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 Changed · +2 lines 656030be4660
- 2mo ago First seen · 135 lines · 204 tokens per session scan A 3a801a23ffd1
test-gap-finder is an agent published in the GitHub repository code-payments/code-android-app (23 stars, last pushed today), licensed MIT. It adds 204 tokens to every session and 1,499 once invoked, about $0.0008 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
ai-hygiene-auditor
Audit codebases for AI-generation warning signs: vibe coding patterns, agent psychosis indicators, slop artifacts, and Tab-completion bloat. Specialized complement to bloat-auditor.
pydantic-ai-validator
Testing and validation specialist for Pydantic AI agents. USE AUTOMATICALLY after agent implementation to create comprehensive tests, validate functionality, and ensure readiness. Uses TestModel and FunctionModel for thorough validation.
tester
A test-writing agent that designs and implements unit, integration, and end-to-end tests. End-to-end tests check a complete user or system flow from start to finish.
verify-app
Full verification - unit tests, migration check, lint, types.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
test-engineer
Expert in testing, TDD, and test automation. Use for writing tests, improving coverage, debugging test failures. Triggers on test, spec, coverage, jest, pytest, playwright, e2e, unit test.