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.
git clone --depth 1 https://github.com/carloshpdoc/ios-workflow-claudeWrote 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/carloshpdoc/ios-workflow-claude/feature-flag-status)<a href="https://agentmods.dev/commands/carloshpdoc/ios-workflow-claude/feature-flag-status"><img src="https://agentmods.dev/badge/commands/carloshpdoc/ios-workflow-claude/feature-flag-status/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/carloshpdoc/ios-workflow-claude/feature-flag-status"><img src="https://agentmods.dev/badge/commands/carloshpdoc/ios-workflow-claude/feature-flag-status.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.00491 |
| Opus 5 | $0.00000 | $0.00246 |
| Sonnet 5 | $0.00000 | $0.00098 |
| Haiku 4.5 | $0.00000 | $0.00049 |
Grade A, and why
feature-flag-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 9d 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 Flag Cleanup Status
Project context: Values in angle brackets below (e.g.
<scheme>,<JIRA_KEY>,<flag-key-enum>) are resolved at runtime — detect them from the project (xcodebuild -list -jsonfor the scheme,git/ghfor repo & owner, the branch name for the Jira key, a codebase search for flag/font files), or ask if they cannot be inferred. This plugin ships no per-project config.
Show the current feature flag cleanup progress.
Steps
1. Read the Tracking File
Read docs/feature-flags/status.md and parse the progress table.
2. Calculate Summary Statistics
Count flags by status:
- Removed: Successfully cleaned up
- In-Progress: Currently being worked on
- Pending: Not yet started
3. Show Progress
Display:
## Feature Flag Cleanup Progress
| Status | Count | Percentage |
|-------------|-------|------------|
| Removed | X | X% |
| In-Progress | X | X% |
| Pending | X | X% |
| **Total** | **X** | **100%** |
Progress: [=========>..........] X%
4. Show In-Progress Flags
If any flags are in-progress, list them:
### Currently In-Progress
| Flag | Owner | Started |
|------|-------|---------|
| ... | ... | ... |
5. Show Recently Removed
List the last 5 removed flags with their PR links:
### Recently Removed
| Flag | Date | PR | Lines Removed |
|------|------|----|---------------|
| ... | ... | ...| ... |
6. Recommend Next Flags
Show the recommended next flags to remove from the status file:
### Recommended Next
| Flag | Recommendation | Complexity |
|------|----------------|------------|
| ... | ... | ... |
Notes
- Total flags are counted from
<flag-key-file> - Part of Firebase Feature Flags Maintenance initiative
- See investigation files in
docs/feature-flags/issues/ - See review reports in
docs/feature-flags/reports/
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.
- 9d ago First seen · 76 lines · 0 tokens per session scan A 0e57791b533b
feature-flag-status is a command published in the GitHub repository carloshpdoc/ios-workflow-claude (7 stars, last pushed 3mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 491 tokens. 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-08-31.
Other commands, from other repositories
debug
Structured debugging with parallel investigation agents.
release
Generate changelog, bump version, and create git tag.
review
Multi-agent code review with parallel validation.
explain
Guided code tour of a file or subsystem this session touched — entry point, the load-bearing pieces, the edges, and what connects to it.
prompt-pilot
Rewrite a rough prompt into a precise, context-enriched prompt (read-only — never implements the task).
e2e-dashboard
Read .cursor/playwright-skills/e2e-dashboard/SKILL.md and follow its instructions exactly. Treat that file's body as your operating instructions for this task. Template files to install live in .cursor/playwright-skills/e2e-dashboard/templates/.