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 skills add GuillemRoca/agent-skills-android --skill test-driven-developmentgit clone --depth 1 https://github.com/GuillemRoca/agent-skills-androidWrote 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/skills/guillemroca/agent-skills-android/test-driven-development)<a href="https://agentmods.dev/skills/guillemroca/agent-skills-android/test-driven-development"><img src="https://agentmods.dev/badge/skills/guillemroca/agent-skills-android/test-driven-development/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/skills/guillemroca/agent-skills-android/test-driven-development"><img src="https://agentmods.dev/badge/skills/guillemroca/agent-skills-android/test-driven-development.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.02147 |
| Opus 5.5 | $0.00018 | $0.00859 |
| Sonnet 5.5 | $0.00009 | $0.00429 |
| Haiku 4.5 | $0.00005 | $0.00215 |
Grade A, and why
test-driven-development 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 — 265 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test-Driven Development
Overview
Write tests before implementation. The Red-Green-Refactor cycle — write a failing test (RED), write minimal code to pass (GREEN), improve the code without changing behavior (REFACTOR) — produces code that is correct by construction and has comprehensive test coverage from the start.
When to Use
- Implementing any new feature or behavior
- Fixing any bug (use the Prove-It pattern)
- Adding new business logic to ViewModels, use cases, or repositories
- Before refactoring (establish a test safety net first)
Skip when: Purely cosmetic UI changes with no behavioral logic.
Core Process
Red-Green-Refactor Cycle
RED: Write a Failing Test
- Write the test first — describe what the code should do:
class TaskListViewModelTest {
private val repository = mockk<TaskRepository>()
private lateinit var viewModel: TaskListViewModel
@Test
fun `initial state is Loading`() {
every { repository.getTasks() } returns flowOf(emptyList())
viewModel = TaskListViewModel(GetTasksUseCase(repository))
assertEquals(TaskListUiState.Loading, viewModel.uiState.value)
}
@Test
fun `emits Success with tasks when repository returns data`() = runTest {
val tasks = listOf(Task("1", "Buy groceries", false))
every { repository.getTasks() } returns flowOf(tasks)
viewModel = TaskListViewModel(GetTasksUseCase(repository))
advanceUntilIdle()
assertEquals(TaskListUiState.Success(tasks), viewModel.uiState.value)
}
@Test
fun `emits Error when repository throws`() = runTest {
every { repository.getTasks() } returns flow { throw IOException("Network error") }
viewModel = TaskListViewModel(GetTasksUseCase(repository))
advanceUntilIdle()
val state = viewModel.uiState.value
assertIs<TaskListUiState.Error>(state)
assertEquals("Network error", state.message)
}
}
- Run the test — it must fail (
./gradlew test)- If it passes immediately, the test doesn't test what you think
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 · 265 lines · 46 tokens per session scan A f230f7c2607b
test-driven-development is a skill published in the GitHub repository GuillemRoca/agent-skills-android (3 stars, last pushed 17d ago), licensed MIT. It adds 46 tokens to every session and 2,147 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 skills, from other repositories
skill-testing
AL test development patterns for Business Central. Use when creating test codeunits, writing Given/When/Then test procedures, using Library Assert, configuring test projects, or implementing TDD workflows.
aldc
Use canonical ALDC architecture, implementation, TDD orchestration, review and specification workflows for AL / Business Central projects.
conduct
AL Conductor Agent - Orchestrates Planning → Implementation → Review → Commit cycle for AL Development. Enforces TDD and quality gates for Business Central extensions. Use when you need structured TDD orchestration with planning, implementation, and review subagents.
tdd-dev-cycle
A test-driven development workflow, meaning developers write automated tests for expected behavior before implementing the code. It defines stages for analysis, testing, development, verification, commits, and repeated fixes.
tdd
Use when implementing features or fixes with test-driven development (TDD).
obsidian-development
Expert guidance for the entire Obsidian plugin development lifecycle. Use this skill when building, testing, or releasing Obsidian plugins. It mandates TDD with Vitest, adherence to the Obsidian API, and automated CI/CD via GitHub Actions.