Borrowing it
Nothing to install: this file belongs to LedgerHQ/ledger-live. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/LedgerHQ/ledger-live/develop/.agents/skills/remove-feature-flag/SKILL.mdgit clone --depth 1 https://github.com/LedgerHQ/ledger-liveWrote 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/skills/ledgerhq/ledger-live/remove-feature-flag)<a href="https://agentmods.dev/skills/ledgerhq/ledger-live/remove-feature-flag"><img src="https://agentmods.dev/badge/skills/ledgerhq/ledger-live/remove-feature-flag.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.00064 | $0.01291 |
| Opus 5 | $0.00032 | $0.00646 |
| Sonnet 5 | $0.00013 | $0.00258 |
| Haiku 4.5 | $0.00006 | $0.00129 |
Grade A, and why
remove-feature-flag 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 7d 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Remove Feature Flag
Run the complete removal workflow. Never write to Firebase.
Invocation
/remove-feature-flag <FEATURE_ID> [FLAG_VALUE_JSON] [TICKET_URL]
Optional modifiers:
proposal only— analyze and propose without changing filesno pr— implement and validate without publishingno watch— create the PR without waiting for CI
Only FEATURE_ID is required. Treat invoking this command as authorization for
the complete workflow unless a modifier limits it. Accept optional arguments in
any trailing order: recognize the JSON object, an http(s) ticket URL, and the
exact modifier phrases independently.
For proposal only, stop after read-only analysis. Do not create Jira work,
stash files, create a branch, commit, push, or publish a PR. Report the resolved
behavior, owner, affected scope, proposed edits, planned validation, and skipped
Jira/PR/CI actions.
1. Resolve the production behavior
Derive the Firebase key with the repository's canonical snake-case mapping.
- Parse and use
FLAG_VALUE_JSONwhen supplied. Validate it against the flag definition and consumers. If it is invalid, lacks a booleanenabled, or omitsparamsthat code consumes, ask for a corrected production value. - Otherwise run:
node .agents/skills/remove-feature-flag/scripts/read-production-flag.mjs "$FEATURE_ID" - If the lookup is unavailable, missing, malformed, or unauthorized, ask the user for the production value. Never fall back to development.
- If Firebase reports conditional values, or the JSON describes A/B variants, show them and ask which behavior to preserve. Do not choose a client-specific variant automatically.
Preserve the resolved production behavior whether enabled is true or
false, including the selected production params.
2. Protect local work and create the branch
Record the initial branch/ref and worktree state. If dirty, stash staged, unstaged, and untracked files with a unique descriptive message; do not ask.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 142 lines · 64 tokens per session scan A 5c45dcfec1f5
remove-feature-flag is a skill published in the GitHub repository LedgerHQ/ledger-live (616 stars, last pushed yesterday), licensed MIT. It adds 64 tokens to every session and 1,291 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
codex-autoresearch
Run autonomous, measurable experiments in a Git repository: change one hypothesis, verify a numeric metric, keep improvements, and revert failures. Use when the user wants Codex to keep iterating toward a numeric target in the foreground or as a detached background run. Do not use for ordinary one-shot coding…
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.