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 agentmods add rules/snyk/snyk-ls/server-dependenciesgit clone --depth 1 https://github.com/snyk/snyk-lsWrote 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/snyk/snyk-ls/server-dependencies)<a href="https://agentmods.dev/rules/snyk/snyk-ls/server-dependencies"><img src="https://agentmods.dev/badge/rules/snyk/snyk-ls/server-dependencies.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 | $0.00141 | $0.00141 |
| Opus 5 | $0.00071 | $0.00071 |
| Sonnet 5 | $0.00028 | $0.00028 |
| Haiku 4.5 | $0.00014 | $0.00014 |
Grade A, and why
server-dependencies 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 3d 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
Dependency Injection
- Do not introduce new direct dependency lookups through
di.*in production logic, handlers, services, or tests. - Bootstrap code may call
di.Init/di.TestInit, but must use the returned dependency bundle and pass dependencies explicitly from there. - For LSP handlers, inject dependencies through
withContextand read them from request context usinginternal/contextdependency keys. - Keep refactors scoped: when touching existing
di.*lookups, change only the dependency needed for the current task unless the user asks for broader cleanup.
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.
- 3d ago First seen · 13 lines · 141 tokens per session scan A 4cc758cc8ae1
server-dependencies is a cursor rule published in the GitHub repository snyk/snyk-ls (83 stars, last pushed 5d ago), licensed Apache-2.0. It adds 141 tokens to every session, about $0.0007 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 cursor rules, from other repositories
root-cause-first
Require source-level fixes for malformed or polluted domain data.
cursorrules
AGENTS.md.
ReviewGateV2
Cursor rule "ReviewGateV2" from LakshmanTurlapati/Review-Gate, covering mandatory checkpoint (must be included in every response), enforcement mechanism, 0. user advisory & safety, 1. core principle & context and phase 1: primary task execution.
troubleshooting-launchdarkly
When debugging LaunchDarkly.
command-rules
Defines custom commands for AI-assisted development workflows.
on-load-rule
MUST READ AT START - Critical Development Principles.