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 rules/nphausg/ai-agent-skills/android_unit_testing_bddgit clone --depth 1 https://github.com/nphausg/ai-agent-skillsWhat 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.00008 | $0.00186 |
| Opus 5 | $0.00004 | $0.00093 |
| Sonnet 5 | $0.00002 | $0.00037 |
| Haiku 4.5 | $0.00001 | $0.00019 |
Grade A, and why
android_unit_testing_bdd 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 yesterday.
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
- Name test functions in BDD style: given_whenthen
- Use GIVEN, WHEN, THEN comments in the test body for clarity.
- Write one behavioral scenario per test.
- Use mocks (MockK, Mockito) to isolate dependencies.
- Prefer runTest or coroutine test rules for suspend functions.
- Avoid fragile tests with real-time delays or random input.
- Example:
@Test
fun givenValidUser_whenFetchUser_thenReturnsUser() {
// GIVEN
val userId = 123
coEvery { userRepo.getUser(userId) } returns User(userId, "Alice")
// WHEN
val result = runBlocking { sut.fetchUser(userId) }
// THEN
assertEquals("Alice", result.name)
}
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.
- yesterday First seen · 25 lines · 8 tokens per session scan A 6b37a4b4904c
android_unit_testing_bdd is a cursor rule published in the GitHub repository nphausg/ai-agent-skills (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 8 tokens to every session and 186 once invoked, about $0.0000 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-31.
Other cursor rules, from other repositories
swift6-migration
Guide for migrating Swift code to Swift 6 with concurrency and strict checking.
swift-argument-parser
Documentation and usage patterns for Swift Argument Parser for command-line tools.
swift-testing-playbook
Comprehensive guide for migrating from XCTest to Swift Testing with best practices from WWDC 2024.
swift-observation
Swift Observation framework documentation and usage patterns for reactive programming.
swift-observable
Migration guide for updating SwiftUI apps from ObservableObject to the @Observable macro.
modern-swift
Write idiomatic SwiftUI code following Apple's latest architectural recommendations and best practices.