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-launchdarkly-flag-commandgit 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-launchdarkly-flag-command)<a href="https://agentmods.dev/skills/bilal140202/the-lord-of-the-skills/feature-flags-launchdarkly-flag-command"><img src="https://agentmods.dev/badge/skills/bilal140202/the-lord-of-the-skills/feature-flags-launchdarkly-flag-command/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-launchdarkly-flag-command"><img src="https://agentmods.dev/badge/skills/bilal140202/the-lord-of-the-skills/feature-flags-launchdarkly-flag-command.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.00058 | $0.01254 |
| Opus 5.5 | $0.00023 | $0.00502 |
| Sonnet 5.5 | $0.00012 | $0.00251 |
| Haiku 4.5 | $0.00006 | $0.00125 |
Grade A, and why
launchdarkly-flag-command 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 1mo 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LaunchDarkly Flag Command Router
You're using a skill that standardizes quick /flag requests. Your job is to parse the user intent, resolve the requested flag with minimal friction, return an actionable summary, and route to deeper workflows when needed.
Scope Boundary
This skill is a read-only lookup entrypoint. It returns flag details and routes forward.
Hard constraints — you MUST NOT:
- Create, toggle, update, or delete flags
- Assess whether a flag is safe to remove, stale, or ready for cleanup
- Provide a "verdict", "safe to remove" conclusion, removal steps, or "before removing" advice
- Offer to archive or delete the flag
When the user asks about removal or staleness, your entire response for that part must be the flag summary table followed by this exact routing message (you may rephrase slightly but must keep the substance):
This quick lookup can only show you the flag's current config. To assess whether it's safe to remove, you need the flag discovery or flag cleanup skill — they scan code references, check status across all environments, and analyze downstream dependencies.
That's it. No analysis. No bullet points. No verdict. The removal question is answered by the routing message, not by you.
Prerequisites
This skill requires the remotely hosted LaunchDarkly MCP server to be configured in your environment.
Required MCP tools:
list-flags— search and disambiguate flag candidatesget-flag— fetch detailed configuration for a resolved flag
Optional MCP tools:
get-flag-status-across-envs— compare lifecycle status across environmentsget-flag-health— quick health snapshot for a single flag
Command Contract
Treat these forms as equivalent intents:
/flag <query>flag <query>- "find flag "
- "show me flag"
Use production as the default environment unless the user specifies another environment.
Workflow
Step 1: Parse and Normalize Input
- Extract the query text after
/flag. - If no query is provided, ask for one concise identifier (flag key, name fragment, or tag).
- Capture optional hints from the request:
- Environment (
staging,production, etc.) - Project key
- Preference for exact key vs fuzzy search
- Environment (
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.
- 1mo ago First seen · 120 lines · 58 tokens per session scan A c519d007a062
launchdarkly-flag-command is a skill published in the GitHub repository Bilal140202/the-lord-of-the-skills (6 stars, last pushed 1mo ago), licensed MIT. It adds 58 tokens to every session and 1,254 once invoked, about $0.0002 per session on Opus 5.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
serpsmith
Publish SEO articles, verify unattended health, and gate source-to-runtime releases.
tool-calling-tutor
Use when a tool-calling agent does not call a tool, sends wrong arguments, loops without stopping, or needs a function schema. Guides a four-branch diagnosis and five-step schema repair. Do not use for framework-specific, MCP-server, or production-observability questions.
ainb-fleet:daemons
Runtime-health view of the four fleet daemons — phone bridge, notifyd, ATC, and the fleet auto-continue daemon — in one table. Each row reports state (running / stopped / unknown), pid, uptime, last activity, error count, and a HEALTH reason that distinguishes a clean stop from a crash (stale heartbeat) or a…
ainb-fleet:atc
ATC (Air Traffic Control) — the single operator-visible fleet supervisor, in exactly one mode: lite (no LLM: deterministic scan, known-transient retry policy, safety caps, evidence) or full (the persistent orchestrating brain). Full mode is a plain ainb session (Claude or Codex) running a generated policy, woken on a…
ainb-fleet:fleet-needs
Workflow-backed Jarvis control panel. Runs the deterministic hangar workflow with verb=needs (discover → enrich → prioritize), renders the Jarvis HUD from its render-ready cards, fires AskUserQuestion per blocked session, and routes each answer back via tmux send-keys (broker fallback only). Requires the workflow gate…
first-plan-lens-mobile
Stack lens para mobile - React Native, Swift (iOS), Kotlin (Android), Flutter. Use durante Discovery quando pubspec.yaml, Package.swift, build.gradle.kts (Android) ou react-native em deps for detectado. Cobre navegação, estado, módulos nativos, build/distribuição.