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/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/spec)<a href="https://agentmods.dev/commands/guillemroca/agent-skills-android/spec"><img src="https://agentmods.dev/badge/commands/guillemroca/agent-skills-android/spec/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/commands/guillemroca/agent-skills-android/spec"><img src="https://agentmods.dev/badge/commands/guillemroca/agent-skills-android/spec.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.00000 | $0.00359 |
| Opus 5.5 | $0.00000 | $0.00144 |
| Sonnet 5.5 | $0.00000 | $0.00072 |
| Haiku 4.5 | $0.00000 | $0.00036 |
Grade A, and why
spec 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 22d 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
/spec — Spec-Driven Development
Write a structured specification before writing any code.
Instructions
Load and follow the spec-driven-development skill from skills/spec-driven-development/SKILL.md.
If the request bundles several independently testable capabilities, first propose a capability map (module ids, Gradle modules, dependency direction, build order) per the skill's Phase 0 and get it approved, then spec each module in dependency order.
Clarifying Questions
Before writing the spec, ask:
- What problem does this solve? Who is the user?
- Which features are in scope? Which are explicitly excluded?
- What stack? (minSdk, Compose vs XML, Hilt, Room, Retrofit, etc.)
- What boundaries? (offline support? tablet? accessibility? deep links?)
Spec Structure
Document these sections in SPEC.md:
- Objective — what and why (1 paragraph)
- Commands — key Gradle tasks (
./gradlew assembleDebug,./gradlew test, etc.) - Project Structure — module hierarchy (
:app,:feature:*,:core:*) - Code Style — Kotlin, Compose, MVVM/MVI, Hilt, Coroutines, etc.
- Testing Strategy — JUnit5 + MockK, Compose test rules, Espresso
- Boundaries — what is explicitly NOT in scope
Output
Save as SPEC.md in the project root. This becomes the development contract. Summarize it, list open questions, ask for approval — then end the turn. Don't start planning or code until the human approves in a later turn.
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.
- 22d ago Changed · +2 lines 196acf218868
- 1mo ago First seen · 31 lines · 0 tokens per session scan A 2ee84d780a09
spec is a command published in the GitHub repository GuillemRoca/agent-skills-android (4 stars, last pushed 23d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 359 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
gofer:eai-first-run
Prepare a new machine or repo for the first EAI Gofer app build.
gofer:check-workspace
Check whether this repo is initialized for Gofer and explain any missing or stale scaffold.
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.
fw-setup-status
Check FDK and Node.js installation status (/fw-setup status); optional --verbose diagnostics.
eai-update
Use this command to install or update EAI Gofer for the current AI coding app. This command works without an EAI project, a Gofer scaffold, or EAI sign-in.
bottleneck-detect
Analyze performance bottlenecks in swarm operations and suggest optimizations.