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-plangit 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-plan)<a href="https://agentmods.dev/commands/ahmed3elshaer/everything-claude-code-mobile/feature-plan"><img src="https://agentmods.dev/badge/commands/ahmed3elshaer/everything-claude-code-mobile/feature-plan.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.00030 | $0.00452 |
| Opus 5 | $0.00015 | $0.00226 |
| Sonnet 5 | $0.00006 | $0.00090 |
| Haiku 4.5 | $0.00003 | $0.00045 |
Grade A, and why
feature-plan 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 Plan Command
Phase 1 of the feature build pipeline. Creates a structured plan document and gets architecture review before implementation begins.
Usage
/feature-plan Add user authentication with biometrics
/feature-plan Implement offline caching for articles
/feature-plan Add push notification handling
Workflow
- Scan:
feature-planneragent analyzes the project structure, existing modules, and dependencies - Plan: Creates plan document at
.omc/plans/feature-{name}.jsonwith:- Module placement decisions
- File breakdown per layer (domain, data, presentation, DI)
- Dependency analysis (new libraries, version constraints)
- Task list with execution order
- Test strategy with coverage targets
- Review:
mobile-architectagent reviews the plan for:- Architecture pattern compliance (MVI/MVVM)
- Module boundaries and dependency direction
- API surface and interface design
- Scalability and testability concerns
- Approve: User is shown the plan summary and architecture review, then asked to approve or request changes
Output
Plan document (.omc/plans/feature-{name}.json) containing:
- modules: Where new code lives, what existing modules are touched
- files: Every file to create or modify, grouped by layer
- dependencies: New libraries, version bumps, Gradle/SPM changes
- tasks: Ordered implementation tasks with agent assignments
- testStrategy: What to test, coverage targets per layer
Examples
# Plan a new feature from scratch
/feature-plan Add biometric login with fallback to PIN
# Plan an enhancement to an existing feature
/feature-plan Add offline support to article feed
# Plan a cross-cutting concern
/feature-plan Add analytics tracking to all screens
Invokes
feature-planneragentmobile-architectagent
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 · 60 lines · 30 tokens per session scan A 10b3a844f1fc
feature-plan is a command published in the GitHub repository ahmed3elshaer/everything-claude-code-mobile (65 stars, last pushed 2mo ago), licensed MIT. It adds 30 tokens to every session and 452 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
audit
Scan a codebase for existing observability instrumentation and identify gaps.
instrument
Generate a comprehensive instrumentation plan for a mobile codebase.
status
Project health dashboard - shows environment status and suggests improvements.
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.