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-completed)<a href="https://agentmods.dev/commands/carloshpdoc/ios-workflow-claude/feature-flag-completed"><img src="https://agentmods.dev/badge/commands/carloshpdoc/ios-workflow-claude/feature-flag-completed.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.00752 |
| Opus 5 | $0.00000 | $0.00376 |
| Sonnet 5 | $0.00000 | $0.00150 |
| Haiku 4.5 | $0.00000 | $0.00075 |
Grade A, and why
feature-flag-completed 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature Flag Completion
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.
Post-removal documentation for feature flag cleanup $ARGUMENTS.
This skill updates status.md, posts to Slack, and optionally updates Notion after a feature flag removal PR is merged.
Note: Run this skill AFTER updating docs/feature-flags/status.md with the removed flags.
Usage
/feature-flag-completed [pr_number]
pr_number- Optional PR number (defaults to current branch's PR)
Steps
1. Gather Information
Get PR details using gh pr view:
- If PR number provided:
gh pr view <pr_number> --json number,title,url,body - If no PR number:
gh pr view --json number,title,url,body
Extract the list of removed flags from the PR body (look for "Flags removed" table or list).
2. Read Current Status
Read docs/feature-flags/status.md and extract:
- Total removed count
- Total flags count
- Percentage
- In-Progress count
- Pending count
3. Post to Slack
Use mcp__slack__conversations_add_message to post to #flags-removal (ID: C0AST27EWTA):
:triangular_flag_on_post: Feature Flag Cleanup — Status Update
Progress: <removed> / <total> removed (<percentage>%)
In-Progress: <in_progress>
Pending: <pending>
Recently Removed:
- <flag_name_1> — #<pr_number> — <date>
- <flag_name_2> — #<pr_number> — <date>
...
:page_facing_up: Tracking: <notion-flags-tracker-url>
4. Update Notion (Optional)
If Notion MCP is available, for each removed flag:
- Search for the flag in the Notion database
- Update the page with:
Code removal date= today's date (YYYY-MM-DD)Owner= git user name
5. Confirm to User
Output summary:
## Feature Flag Cleanup Complete
| Metric | Value |
|--------|-------|
| Flags removed | <count> |
| PR | #<pr_number> |
| Progress | <removed>/<total> (<percentage>%) |
### Flags Removed
- <flag_1>
- <flag_2>
...
### Actions
| Action | Status |
|--------|--------|
| status.md | Already updated |
| Slack posted | Message sent to #flags-removal |
| Notion | Updated / Not available |
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.
- 8d ago First seen · 101 lines · 0 tokens per session scan A f7dd165be4bd
feature-flag-completed 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 752 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.
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/.
mobile-app-testing
Read .cursor/playwright-skills/mobile-app-testing/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/mobile-app-testing/templates/.