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 commands/guillemroca/agent-skills-android/buildgit 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/commands/guillemroca/agent-skills-android/build)<a href="https://agentmods.dev/commands/guillemroca/agent-skills-android/build"><img src="https://agentmods.dev/badge/commands/guillemroca/agent-skills-android/build.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.00000 | $0.00430 |
| Opus 5 | $0.00000 | $0.00215 |
| Sonnet 5 | $0.00000 | $0.00086 |
| Haiku 4.5 | $0.00000 | $0.00043 |
Grade A, and why
build 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
/build — Incremental Implementation with TDD
Build the next task incrementally using test-driven development.
Modes
/build— interactive: work task by task, checking in between tasks./build auto— autonomous: plan the remaining tasks first, present the full plan for ONE approval, then implement every task without further check-ins. Stop and ask only on: failing tests you cannot fix within the task's scope, a needed deviation from the approved plan, or destructive operations. Everything else follows the same per-task cycle below.
Instructions
Load and follow these skills:
incremental-implementationfromskills/incremental-implementation/SKILL.mdtest-driven-developmentfromskills/test-driven-development/SKILL.md
Per-Task Cycle
For each task in tasks/todo.md:
- Review the task's acceptance criteria
- Gather examples — find similar patterns in the codebase
- Write a failing test (RED) — describes the expected behavior
- Write minimal code to pass the test (GREEN)
- Run
./gradlew test— verify all tests pass - Run
./gradlew assembleDebug— verify the build succeeds - Verify the slice end-to-end when it is user-visible — run its Maestro
flow per
android-e2e-verification(maestro test .maestro/<slice>.yaml) - Commit the increment
- Repeat for the next acceptance criterion
Error Handling
If a test fails unexpectedly or the build breaks:
- Load
debugging-and-error-recoveryskill - Follow the six-step triage process
- Fix the root cause before proceeding
Rules
- Each increment leaves the codebase in a working state
- Never skip the build check between increments
- Commits are small and focused (~100 lines)
- Incomplete features go behind feature flags
- Don't mix refactoring with feature work
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 · 49 lines · 0 tokens per session scan A 9cd64960c852
build is a command published in the GitHub repository GuillemRoca/agent-skills-android (2 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 430 tokens. 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 commands, from other repositories
tdd
Test-driven development with TodoWrite planning and comprehensive testing.
9_gofer_tests
Generate comprehensive test suites from four testing perspectives for a target component.
gofer:tdd
Guide a red-green-refactor loop tied to spec acceptance criteria.
spec-impl
Execute spec tasks using TDD methodology.
al-agent-instructions-create
Generate optimized natural language instructions for Business Central agents (Designer or SDK). Follows Responsibilities-Guidelines-Instructions framework. Use when writing agent instructions or creating InstructionsV1.txt.
fdk-migrate
Migrate a legacy Freshworks app from platform-version 2.3 (2.x), FDK 9.x, and Node 18 to Platform 3.0 with FDK 10.0.1 and Node 24.11.0. Transforms manifest, request templates, Crayons UI, and validates on the new toolchain. Does not install fdk/Node—use fw-setup (or prompt user to add it) per SKILL.md.