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/carloshpdoc/ios-workflow-claude/feature-flag-removegit 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-remove)<a href="https://agentmods.dev/commands/carloshpdoc/ios-workflow-claude/feature-flag-remove"><img src="https://agentmods.dev/badge/commands/carloshpdoc/ios-workflow-claude/feature-flag-remove.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.00000 | $0.02974 |
| Opus 5 | $0.00000 | $0.01487 |
| Sonnet 5 | $0.00000 | $0.00595 |
| Haiku 4.5 | $0.00000 | $0.00297 |
Grade C, and why
feature-flag-remove scanned grade C with 1 finding 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 6d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf <scheme>/Coordinator/UniversalLink/Handlers/<V1Handler>/ How it starts
The opening of the file, as written. The whole thing — 377 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature Flag Removal
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.
Remove the feature flag $ARGUMENTS following the investigation plan.
Prerequisite: Must have an investigation file at docs/feature-flags/issues/$ARGUMENTS.md. Run /feature-flag-check $ARGUMENTS first if it doesn't exist.
Steps
1. Create Jira Task
Create a Jira task in the current sprint using mcp__claude_ai_Atlassian__createJiraIssue:
- Project: <JIRA_KEY>
- Type: Task
- Summary:
Remove feature flag: $ARGUMENTS - Epic Link: <JIRA_KEY>-EPIC (Firebase Flags Clean Up)
- Assignee: Current user (get from
git config user.email)
Description template:
## Objective
Remove the `$ARGUMENTS` feature flag as part of the Firebase Feature Flags Maintenance initiative.
## Investigation
<Summary from docs/feature-flags/issues/$ARGUMENTS.md>
## Complexity
<Low/Medium/High based on investigation>
## Related
- Epic: <JIRA_KEY>-EPIC (Firebase Flags Clean Up)
- Notion: <notion-flags-tracker-url>
Save the Jira ticket number (e.g., <JIRA_KEY>-XXXX) for later use in commit messages and PR title.
2. Create Branch
Create a feature branch for this removal:
git checkout dev
git pull origin dev
git checkout -b feature/remove-flag-$ARGUMENTS
3. Check for Conflicting PRs
IMPORTANT: Before modifying RemoteConfig files, check for open PRs that touch the same files:
gh pr list --state open --json number,title,files --jq '.[] | select(.files[]?.path | test("<flag-key-enum>|<flag-defaults-file>")) | "PR #\(.number): \(.title)"'
If PRs are found:
- ⚠️ STOP and warn the user with the list of conflicting PRs
- Recommend syncing with those developers before proceeding
- Options:
- Wait for the other PR to merge, then rebase
- Coordinate with the other developer to avoid conflicts
- Proceed only with explicit user confirmation
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.
- 6d ago First seen · 377 lines · 0 tokens per session scan C 4ebf5b27d926
feature-flag-remove 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 2,974 tokens. A static security scan graded it C with 1 finding (recursive force delete). 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.
prompt-pilot
Rewrite a rough prompt into a precise, context-enriched prompt (read-only — never implements the task).
aw-upgrade
Upgrade gh-aw extension, recompile and validate all workflows, and open a PR with changes.
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/.