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/ahmed3elshaer/everything-claude-code-mobile/feature-buildgit clone --depth 1 https://github.com/ahmed3elshaer/everything-claude-code-mobileWrote 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/ahmed3elshaer/everything-claude-code-mobile/feature-build)<a href="https://agentmods.dev/commands/ahmed3elshaer/everything-claude-code-mobile/feature-build"><img src="https://agentmods.dev/badge/commands/ahmed3elshaer/everything-claude-code-mobile/feature-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.1 | $0.00045 | $0.00512 |
| Opus 5 | $0.00023 | $0.00256 |
| Sonnet 5 | $0.00009 | $0.00102 |
| Haiku 4.5 | $0.00005 | $0.00051 |
Grade A, and why
feature-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 2d 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
Feature Build Command
Master entry point for end-to-end mobile feature construction. Runs all 6 phases sequentially, tracking progress in state files.
Usage
/feature-build Add user authentication with biometrics
/feature-build --platform=android Implement offline caching
/feature-build --from-phase=test auth
/feature-build --skip-phase=quality Add profile screen
Flags
| Flag | Values | Description |
|---|---|---|
--platform |
android, ios, kmp |
Override auto-detection |
--from-phase |
implement, test, build-fix, quality, verify |
Resume from a specific phase |
--skip-phase |
quality |
Skip a phase |
Phases
| # | Phase | Command | Description |
|---|---|---|---|
| 1 | Plan | /feature-plan |
Architecture, file breakdown, test strategy |
| 2 | Implement | /feature-implement |
Parallel agent implementation |
| 3 | Test | /feature-test |
Unit, UI, and E2E test creation |
| 4 | Build & Fix | /feature-build-fix |
Compile and fix errors iteratively |
| 5 | Quality Gate | /feature-quality-gate |
Code review, security, performance |
| 6 | Verify | /feature-verify |
pass@k metrics, coverage, sign-off |
| 7 | Learn | (automatic) | Pattern extraction, instinct updates, completeness scoring |
State
Progress tracked in .omc/state/feature-{name}.json. Use /feature-status to inspect.
Examples
# Full feature build with auto-detected platform
/feature-build Add push notification support
# Android-only, skip quality gate for prototype
/feature-build --platform=android --skip-phase=quality Add search screen
# Resume a failed build from the test phase
/feature-build --from-phase=test auth
# KMP feature targeting shared module
/feature-build --platform=kmp Add offline sync for user data
Invokes
feature-builderskill (orchestrates all phases)
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.
- 2d ago First seen · 61 lines · 45 tokens per session scan A 98a7cada7d2a
feature-build is a command published in the GitHub repository ahmed3elshaer/everything-claude-code-mobile (65 stars, last pushed 2mo ago), licensed MIT. It adds 45 tokens to every session and 512 once invoked, about $0.0002 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 commands, from other repositories
test-simulator
Launch simulator testing agent for test scenarios and visual verification.
ios-test
Bu komut iOS/SwiftUI uygulamasini derleyip simulator'da acarak computer use ile gorsel test yapar.
maestro-selectors-instructions
Guide to using Maestro selectors for targeting UI elements in tests.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.