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-statusgit 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-status)<a href="https://agentmods.dev/commands/ahmed3elshaer/everything-claude-code-mobile/feature-status"><img src="https://agentmods.dev/badge/commands/ahmed3elshaer/everything-claude-code-mobile/feature-status.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.00025 | $0.00404 |
| Opus 5 | $0.00013 | $0.00202 |
| Sonnet 5 | $0.00005 | $0.00081 |
| Haiku 4.5 | $0.00003 | $0.00040 |
Grade A, and why
feature-status 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 Status Command
Progress tracker for feature builds. Reads state files and displays a summary of phase completion, agent status, and blockers.
Usage
/feature-status auth # Status of a specific feature
/feature-status # List all tracked features
Reads
State file at .omc/state/feature-{name}.json.
Output Example
Feature: auth
═════════════
Phase Progress:
1. Plan ████████████ completed
2. Implement ████████░░░░ in-progress
3. Test ░░░░░░░░░░░░ pending
4. Build & Fix ░░░░░░░░░░░░ pending
5. Quality Gate ░░░░░░░░░░░░ pending
6. Verify ░░░░░░░░░░░░ pending
Implementation Agents:
architecture-impl: completed (4 files)
network-impl: completed (3 files)
ui-impl: in-progress (3/5 files)
data-impl: waiting
wiring-impl: waiting
Files Created: 14 / ~22
Blockers: none
List All Features
/feature-status
Tracked Features:
auth Phase 2/6 (Implement) in-progress
offline-cache Phase 5/6 (Quality) in-progress
push-notifs Phase 6/6 (Verify) completed ✓
No Agents Invoked
This command reads the state file directly without delegating to any agent.
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 · 59 lines · 25 tokens per session scan A 30fbe7a6df78
feature-status is a command published in the GitHub repository ahmed3elshaer/everything-claude-code-mobile (65 stars, last pushed 2mo ago), licensed MIT. It adds 25 tokens to every session and 404 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
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).
instrument
Generate a comprehensive instrumentation plan for a mobile codebase.
health-report
Show health status for all feature modules.
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.