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-implementgit 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-implement)<a href="https://agentmods.dev/commands/ahmed3elshaer/everything-claude-code-mobile/feature-implement"><img src="https://agentmods.dev/badge/commands/ahmed3elshaer/everything-claude-code-mobile/feature-implement.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.00028 | $0.00425 |
| Opus 5 | $0.00014 | $0.00212 |
| Sonnet 5 | $0.00006 | $0.00085 |
| Haiku 4.5 | $0.00003 | $0.00042 |
Grade A, and why
feature-implement 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 today.
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 Implement Command
Phase 2 of the feature build pipeline. Executes the approved plan using specialized agents running in dependency order.
Usage
/feature-implement auth
/feature-implement offline-cache
/feature-implement push-notifications
Prerequisite
An approved plan must exist at .omc/plans/feature-{name}.json. Run /feature-plan first.
Execution Order (Dependency DAG)
Phase 1: architecture-impl
|
┌────┴────┐
Phase 2: network ui-impl
-impl |
| |
Phase 3: data-impl |
| |
└────┬────┘
Phase 4: wiring-impl
- architecture-impl - Domain models, interfaces, DI module skeleton, shared contracts
- network-impl + ui-impl (parallel) - API clients, DTOs, mappers / Compose screens, components, navigation
- data-impl (after network) - Repository implementations, local DB, caching
- wiring-impl (after all) - DI bindings, navigation wiring, feature flag integration
Each agent reads its assigned section from the plan document and writes only the files it owns.
State
Progress tracked in .omc/state/feature-{name}.json:
architecture-impl: completed
network-impl: completed
ui-impl: in-progress (3/5 files)
data-impl: waiting
wiring-impl: waiting
Invokes
architecture-implagentnetwork-implagentdata-implagentui-implagentwiring-implagent
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.
- today First seen · 62 lines · 28 tokens per session scan A fa653945032c
feature-implement is a command published in the GitHub repository ahmed3elshaer/everything-claude-code-mobile (65 stars, last pushed 2mo ago), licensed MIT. It adds 28 tokens to every session and 425 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 commands, from other repositories
audit
Scan a codebase for existing observability instrumentation and identify gaps.
instrument
Generate a comprehensive instrumentation plan for a mobile codebase.
feat
Kick off tasks creation for a new feature (4-item interview before invoking pm-agent; an epic-sized requirement routes to phased decomposition, a feature already built on one platform routes to cross-platform parity, a change that touches no endpoint routes to client-only).
git
Git operations with intelligent commit messages and workflow optimization.
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.