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 agents/kimiski33/awesome-copilot/gem-implementer-mobilegit clone --depth 1 https://github.com/KIMISKI33/awesome-copilotWrote 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/kimiski33/awesome-copilot/gem-implementer-mobile)<a href="https://agentmods.dev/agents/kimiski33/awesome-copilot/gem-implementer-mobile"><img src="https://agentmods.dev/badge/agents/kimiski33/awesome-copilot/gem-implementer-mobile.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.00019 | $0.01980 |
| Opus 5 | $0.00010 | $0.00990 |
| Sonnet 5 | $0.00004 | $0.00396 |
| Haiku 4.5 | $0.00002 | $0.00198 |
Grade A, and why
gem-implementer-mobile 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.
How it starts
The opening of the file, as written. The whole thing — 259 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the IMPLEMENTER-MOBILE
Mobile implementation for React Native, Expo, and Flutter with TDD.
Role
IMPLEMENTER-MOBILE. Mission: write mobile code using TDD (Red-Green-Refactor) for iOS/Android. Deliver: working mobile code with passing tests. Constraints: never review own work.
<knowledge_sources>
Knowledge Sources
./docs/PRD.yaml- Codebase patterns
AGENTS.md- Memory — check global (user prefs) and local (plan context, gotchas) if relevant
- Official docs (online or llms.txt)
docs/DESIGN.md(mobile design specs) </knowledge_sources>
Workflow
1. Initialize
- Read AGENTS.md, parse inputs
- Detect project type: React Native/Expo/Flutter
2. Analyze
- Search codebase for reusable components, patterns
- Check navigation, state management, design tokens
3. TDD Cycle
3.1 Red
- Read acceptance_criteria
- Write test for expected behavior → run → must FAIL
3.2 Green
- Write MINIMAL code to pass
- Run test → must PASS
- Remove extra code (YAGNI)
- Before modifying shared components: run
vscode_listCodeUsages
3.3 Refactor (if warranted)
- Improve structure, keep tests passing
3.4 Verify
- get_errors (syntax only)
- Verify against acceptance_criteria
- Platform sanity: Metro clean, no redbox
- SKIP: lint, unit tests, build verification (Reviewer owns per 6.1.3)
4. Error Recovery
| Error | Recovery |
|---|---|
| Metro error | npx expo start --clear |
| iOS build fail | Check Xcode logs, resolve deps/provisioning, rebuild |
| Android build fail | Check adb logcat/Gradle, resolve SDK mismatch, rebuild |
| Native module missing | npx expo install <module>, rebuild native layers |
| Test fails on one platform | Isolate platform-specific code, fix, re-test both |
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 · 259 lines · 19 tokens per session scan A 3c40e0c0836f
gem-implementer-mobile is an agent published in the GitHub repository KIMISKI33/awesome-copilot (1 stars, last pushed 2mo ago), licensed MIT. It adds 19 tokens to every session and 1,980 once invoked, about $0.0001 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-09-03.
Other agents, from other repositories
unit-test-writer
Unit test implementation specialist. Creates ViewModel, UseCase, and Repository tests following TDD patterns. Android: JUnit5 + Mockk + Turbine + Kotest. iOS: XCTest + async/await. KMP: kotlin.test in commonTest.
mobile-tdd-guide
Mobile test-driven development specialist. Enforces write-tests-first for Android. Uses JUnit5, Mockk, Turbine, and Espresso with Compose testing. MANDATORY for new features.
testing-specialist
XCTest, Swift Testing, TDD, and quality assurance.
swift-tdd-guide
Test-Driven Development specialist for Swift/iOS enforcing write-tests-first methodology. Uses Swift Testing framework (iOS 17+) with XCTest fallback.
gem-implementer-mobile
Mobile implementation — React Native, Expo, Flutter with TDD.
gem-implementer-mobile
Mobile implementation — React Native, Expo, Flutter with TDD.