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 skills add Bilal140202/the-lord-of-the-skills --skill feature-flags-should-flag-changegit clone --depth 1 https://github.com/Bilal140202/the-lord-of-the-skillsWrote 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/bilal140202/the-lord-of-the-skills/feature-flags-should-flag-change)<a href="https://agentmods.dev/skills/bilal140202/the-lord-of-the-skills/feature-flags-should-flag-change"><img src="https://agentmods.dev/badge/skills/bilal140202/the-lord-of-the-skills/feature-flags-should-flag-change/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/skills/bilal140202/the-lord-of-the-skills/feature-flags-should-flag-change"><img src="https://agentmods.dev/badge/skills/bilal140202/the-lord-of-the-skills/feature-flags-should-flag-change.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.00078 | $0.04034 |
| Opus 5 | $0.00039 | $0.02017 |
| Sonnet 5 | $0.00016 | $0.00807 |
| Haiku 4.5 | $0.00008 | $0.00403 |
Grade A, and why
should-flag-change 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 5d 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Should This Change Be Behind a Flag?
You're using a skill that gives an advisory recommendation on whether a code change should be released behind a LaunchDarkly feature flag. Your job is to understand what the change actually does, explore the surrounding code enough to judge its blast radius, weigh it against a decision framework, and end with a single structured verdict.
You are invoked two ways:
- Ad hoc — a developer asks "should this be behind a flag?" about work in progress.
- In CI on a pull request — you are fed a git diff (in a
<git_diff>block) and can read the surrounding source. Your verdict is parsed to post a check on the PR.
Both paths end the same way: a call to the recommend-flag tool.
Scope Boundary
This skill is read-only and advisory. You produce a recommendation; you never act on it.
Hard constraints — you MUST NOT:
- Create, toggle, update, archive, or delete any feature flag.
- Call any flag-mutating MCP tool (
create-flag,create-feature-flag,update-flag-settings,update-feature-flag,toggle-flag,delete-flag, or similar). - Modify, stage, or commit code. You read; you do not write.
- Instruct the user to run a command that mutates flags as if it were part of this workflow.
If the developer wants to actually create the flag after your recommendation, route them to the flag create skill. Do not do it yourself.
Core Principles
- Advisory, not authoritative. You inform a human decision. Be clear and specific; do not gate the merge.
- False negatives are worse than false positives. Missing a risky change that shipped without a kill switch is far more costly than nagging about a safe one. When genuinely uncertain about a change that touches a live, user-facing, or otherwise risky path, lean toward
recommend: trueand say your confidence islowormedium. - Explore before deciding. A diff shows what lines changed, not what they mean. Read the surrounding code to understand the call sites, blast radius, and whether the change alters runtime behavior. In CI you have the repo tree — use it.
- Judge behavior, not line count. A one-line change to an auth check matters more than a 500-line rename. Ask "does this change what production does, and for whom?"
- Cite evidence. Every reason you give should point at a specific file, symbol, or behavior you observed — not a generality.
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.
- 5d ago First seen · 165 lines · 78 tokens per session scan A e77c6aeb6ae2
should-flag-change is a skill published in the GitHub repository Bilal140202/the-lord-of-the-skills (4 stars, last pushed 6d ago), licensed MIT. It adds 78 tokens to every session and 4,034 once invoked, about $0.0004 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-09-06.
Other skills, from other repositories
review
Review Playwright tests for quality. Use when user says "review tests", "check test quality", "audit tests", "improve tests", "test code review", or "playwright best practices check".
first-plan-lens-engine
Skill que define o motor de detecção e roteamento de stack lenses do first-plan. Mapeia manifestos (go.mod, package.json, etc) -> stack -> papel -> lens skill correspondente. Use quando precisar decidir qual lens aplicar a uma pasta durante Discovery, ou quando estender suporte a uma nova stack.
first-plan-pattern-extraction
Skill que define como extrair padrões do código com confidence scoring. Use durante Discovery quando precisar identificar convenções, anti-padrões ou padrões idiomáticos do projeto. Cada padrão extraído deve vir com exemplo concreto do código (path:line).
serpsmith
Publish SEO articles reliably across AI-agent runtimes.
coding-standards
Detects code smells, anti-patterns, and readability issues. Use when implementing features, reviewing code, or refactoring.
detecting-process-injection-techniques
Detects and analyzes process injection techniques used by malware including classic DLL injection, process hollowing, APC injection, thread hijacking, and reflective loading. Uses memory forensics, API monitoring, and behavioral analysis to identify injection artifacts. Activates for requests involving process…