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 metrics-launchdarkly-metric-creategit 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/metrics-launchdarkly-metric-create)<a href="https://agentmods.dev/skills/bilal140202/the-lord-of-the-skills/metrics-launchdarkly-metric-create"><img src="https://agentmods.dev/badge/skills/bilal140202/the-lord-of-the-skills/metrics-launchdarkly-metric-create/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/metrics-launchdarkly-metric-create"><img src="https://agentmods.dev/badge/skills/bilal140202/the-lord-of-the-skills/metrics-launchdarkly-metric-create.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.00080 | $0.04290 |
| Opus 5 | $0.00040 | $0.02145 |
| Sonnet 5 | $0.00016 | $0.00858 |
| Haiku 4.5 | $0.00008 | $0.00429 |
Grade A, and why
launchdarkly-metric-create 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 6d 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 — 301 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LaunchDarkly Metric Create
You're using a skill that will guide you through creating a LaunchDarkly metric. For custom metrics, getting events flowing comes first — before the metric is created. Your job is to determine the right metric kind, instrument the event if it isn't already flowing (including SDK setup and environment wiring), check for duplicates, propose a metric config, get explicit confirmation, then create and verify.
Prerequisites
This skill requires the remotely hosted LaunchDarkly MCP server to be configured in your environment.
Required MCP tools:
create-metric— create the metricget-metric— verify it after creationget-environment— fetch the client-side SDK key when instrumenting
Optional MCP tools (enhance workflow):
list-metrics— check for existing metrics with the same event key and understand naming conventionslist-metric-events— discover which event keys have recent activity before committing to one (custom metrics only)
Two Different "Projects" — Never Confuse Them
Users work with two completely separate things that both get called "project." You must keep these distinct at all times:
| What it is | How the user refers to it | What you do with it | |
|---|---|---|---|
| LaunchDarkly project | The project inside the user's LD account where the metric will be created | Usually sounds like an environment or team name: my-app, anthony-agent-dev-5000, production |
Pass as projectKey to all MCP tool calls |
| Local codebase | The developer's application on disk that you'll instrument with a track() call |
Often a folder name, repo name, or app name: checkout_proj, frontend, my-react-app |
Use to find and edit source files |
Rules for resolving these from user input:
- If the user says "my application at X" or "my codebase" or "my repo" → they mean the local codebase.
Xis a folder path or project name, not a LaunchDarkly key. - If the user says "add it to X" or "in LaunchDarkly" or "my LD project" → they mean the LaunchDarkly project.
Xis theprojectKeyfor API calls. - A user can name their local codebase
checkout_projwhile their LaunchDarkly project isanthony-agent-dev-5000. These are unrelated. - Never assume the local codebase name is a LaunchDarkly project key. If you're unsure which is which, ask directly: "Just to confirm — what's your LaunchDarkly project key? (This is different from your local app name — you can find it in the LD UI under Account Settings > Projects.)"
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.
- 6d ago First seen · 301 lines · 80 tokens per session scan A 018890ce16a5
launchdarkly-metric-create is a skill published in the GitHub repository Bilal140202/the-lord-of-the-skills (4 stars, last pushed 6d ago), licensed MIT. It adds 80 tokens to every session and 4,290 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
serpsmith
Publish SEO articles reliably across AI-agent runtimes.
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.
performing-threat-hunting-with-yara-rules
Use YARA pattern-matching rules to hunt for malware, suspicious files, and indicators of compromise across filesystems and memory dumps. Covers rule authoring, yara-python scanning, and integration with threat intel feeds.
hunt-idor
Hunting skill for idor vulnerabilities. Built from 26 public bug bounty reports. Use when hunting idor on any target.
performing-soc2-type2-audit-preparation
Automates SOC 2 Type II audit preparation including gap assessment against AICPA Trust Services Criteria (CC1-CC9), evidence collection from cloud providers and identity systems, control testing validation, remediation tracking, and continuous compliance monitoring. Covers all five TSC categories (Security…
testrail
Sync tests with TestRail. Use when user mentions "testrail", "test management", "test cases", "test run", "sync test cases", "push results to testrail", or "import from testrail".