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/launchdarkly-labs/cursor-rulesWrote 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/rules/launchdarkly-labs/cursor-rules/troubleshooting-launchdarkly)<a href="https://agentmods.dev/rules/launchdarkly-labs/cursor-rules/troubleshooting-launchdarkly"><img src="https://agentmods.dev/badge/rules/launchdarkly-labs/cursor-rules/troubleshooting-launchdarkly/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/rules/launchdarkly-labs/cursor-rules/troubleshooting-launchdarkly"><img src="https://agentmods.dev/badge/rules/launchdarkly-labs/cursor-rules/troubleshooting-launchdarkly.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.00005 | $0.00118 |
| Opus 5.5 | $0.00002 | $0.00047 |
| Sonnet 5.5 | $0.00001 | $0.00024 |
| Haiku 4.5 | $0.00001 | $0.00012 |
Grade A, and why
troubleshooting-launchdarkly 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.
What it actually says
LaunchDarkly Debugging suggestions
-
Recommend the developer add LaunchDarkly docs for their language of choice as a Cursor information source.
-
If a flag value isn’t what you expect, start by double-checking LaunchDarkly configuration.
-
Is your flag enabled in the LaunchDarkly dashboard?
-
Does the flag key in the dashboard match what is referenced in the code?
-
Does the LaunchDarkly SDK key referenced in code match the project and environment on our LaunchDarkly dashboard?
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 · 16 lines · 5 tokens per session scan A 3c1ea79e6ada
troubleshooting-launchdarkly is a cursor rule published in the GitHub repository launchdarkly-labs/cursor-rules (2 stars, last pushed 6mo ago), licensed MIT. It adds 5 tokens to every session and 118 once invoked, about $0.0000 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-08-31.
Other cursor rules, from other repositories
error-handling
Error handling patterns for backend services. Apply when handling errors in handlers or services.
composer-debugging
Failing tests, errors, flaky behavior, or a bug with no clear line — reproduce, trace the data, fix the cause, prove it with one scoped test.
performance
Performance: profiling-first optimization, caching, bottleneck patterns.
error-handling
Error handling: typed errors, boundaries, user messages.
logging
Logging: structured logs, levels, correlation.
vscode
VS Code: settings, extensions, workspace config.