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-check)<a href="https://agentmods.dev/commands/carloshpdoc/ios-workflow-claude/feature-flag-check"><img src="https://agentmods.dev/badge/commands/carloshpdoc/ios-workflow-claude/feature-flag-check/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-check"><img src="https://agentmods.dev/badge/commands/carloshpdoc/ios-workflow-claude/feature-flag-check.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.01085 |
| Opus 5 | $0.00000 | $0.00543 |
| Sonnet 5 | $0.00000 | $0.00217 |
| Haiku 4.5 | $0.00000 | $0.00109 |
Grade A, and why
feature-flag-check 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature Flag Investigation
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.
Investigate the feature flag $ARGUMENTS and produce a detailed investigation for removal.
Output: Creates an investigation file at docs/feature-flags/issues/$ARGUMENTS.md that serves as the "issue" for this cleanup. The /feature-flag-remove command will read this investigation before executing the removal.
Steps
1. Find the Flag Definition
Search for the flag in RemoteConfig files:
Grep: "$ARGUMENTS" in <flag-key-file>
Grep: "$ARGUMENTS" in <flag-defaults-file>.swift
Document:
- The exact case name in
<flag-key-enum> - The default value from
<flag-defaults-file> - The value type (Bool, String, Int, etc.)
2. Find All Flag Usages
Search for all code using this flag:
Grep: "<flag-key-enum>.$ARGUMENTS" in *.swift
Grep: ".$ARGUMENTS" in *.swift (for shorthand usage)
Grep: the flag's string key in all files
For each usage, note:
- File path
- How the flag is read (remoteConfig.bool(), remoteConfig.string(), etc.)
- What code path is gated (true vs false branch)
- Whether it's the only flag check or combined with others
3. Trace Code Paths
For each flag usage, trace what code is affected:
If flag guards a feature:
- Find all ViewControllers/Views involved
- Find all ViewModels involved
- Find all Repositories/DataSources involved
- Find all Models specific to the feature
- Find navigation/coordinator logic
- Find any managers or helpers
If flag guards a UI element:
- Find the specific view/component
- Check if it has dedicated logic or is inline
If flag guards a string/config value:
- Find where the value is used
- Check if removal requires a replacement value
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 · 163 lines · 0 tokens per session scan A 89c68aa65d88
feature-flag-check 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 1,085 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.
ui-aqa-flow-test-report-analysis
Phase 7 Test Report Analysis of ui-aqa-flow.
statusbar-doctor
Run cs doctor to diagnose why the status bar isn't showing what you expect.
linkerd
Linkerd-specific diagnostics — mTLS verification, proxy injection issues, authorization policy debugging, traffic management, and multi-cluster connectivity problems.
debug
Systematic debugging with hypotheses and evidence gathering.
code-locate
Given a behavior description, locate candidate code paths and line ranges in the active codebase that probably implement it. Output up to 10 candidates with HIGH/MEDIUM/LOW confidence, one-line rationale per candidate, and an explicit search trail; propose a SOURCEOFTRUTH.md update so the next workflow step (typically…