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 skills/snyk/snyk-ls/commitnpx skills add snyk/snyk-ls --skill commitgit clone --depth 1 https://github.com/snyk/snyk-lsWhat 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.00057 | $0.01487 |
| Opus 5 | $0.00028 | $0.00744 |
| Sonnet 5 | $0.00011 | $0.00297 |
| Haiku 4.5 | $0.00006 | $0.00149 |
Grade A, and why
commit 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 2d 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 — 261 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit Workflow
Prepare, verify, and commit code changes following project standards.
Workflow Overview
Verify → Fix Issues (TDD) → Pre-commit Checks → Commit → Tests → [Push]
Quick Start Checklist
Copy and track progress:
Commit Progress:
- [ ] Step 1: Run verification skill
- [ ] Step 2: Fix issues using TDD
- [ ] Step 3: Run pre-commit checks
- [ ] Step 4: Create atomic commit
- [ ] Step 5: Run ALL test suites (3 REQUIRED):
- [ ] make test
- [ ] INTEG_TESTS=1 make test
- [ ] SMOKE_TESTS=1 make test
- [ ] Step 6: Push (optional, ask first)
CRITICAL: Step 5 has THREE mandatory test suites. Skipping any is FORBIDDEN.
Step 1: Run Verification Skill
Execute the verification skill to analyze code changes:
Verification Progress:
- [ ] Load project rules and standards
- [ ] Trace code paths for modified files
- [ ] Check for semantic changes
- [ ] Identify code smells
- [ ] Run security scans
- [ ] Review PR feedback (if PR exists)
Read and follow: .cursor/skills/verification/SKILL.md
Output: List of issues found, categorized by severity.
Step 2: Fix Issues Using TDD
For each issue identified by verification:
TDD Gate (MANDATORY)
Before ANY fix:
- Write failing test first
- Confirm test fails without fix
- Implement minimal fix
- Confirm test passes
Never skip TDD. Use implementation skill for complex fixes.
Issue Priority
- Security vulnerabilities - Fix immediately (except test data)
- Breaking changes - Confirm intentional, add tests
- Code smells - Fix immediately
- PR feedback - Address blockers first
Step 3: Pre-commit Checks
Run:
make format
make test
INTEG_TESTS=1 make test
SMOKE_TESTS=1 make test
Security Scans
Get absolute path first:
pwd
Then run:
snyk_sca_scanwith absolute project pathsnyk_code_scanwith absolute project path
Fix any security issues (skip test data false positives).
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.
- 2d ago First seen · 261 lines · 57 tokens per session scan A 49f132a51289
commit is a skill published in the GitHub repository snyk/snyk-ls (83 stars, last pushed 3d ago), licensed Apache-2.0. It adds 57 tokens to every session and 1,487 once invoked, about $0.0003 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 skills, from other repositories
git-commit
Create git commits using Nimbalyst's interactive commit proposal widget. ONLY use when the user explicitly clicks "Commit with AI" button or asks for "smart commit". For regular commit requests, use standard git commands instead.
commit
Use when writing a commit message, and MUST invoke before creating any git commit. Provides commit message format and safety rules.
launch
Launch and automate VS Code (Code OSS) using agent-browser via Chrome DevTools Protocol. Use when you need to interact with the VS Code UI, automate the chat panel, test UI features, or take screenshots of VS Code. Triggers include 'automate VS Code', 'interact with chat', 'test the UI', 'take a screenshot', 'launch…
accessibility
Primary accessibility skill for VS Code. REQUIRED for new feature and contribution work, and also applies to updates of existing UI. Covers accessibility help dialogs, accessible views, verbosity settings, signals, ARIA announcements, keyboard navigation, and ARIA labels/roles.
sessions
Agent Sessions window architecture — covers the sessions-first app, layering, folder structure, chat widget, menus, contributions, entry points, and development guidelines. Use when implementing features or fixing issues in the Agent Sessions window.
component-fixtures
Use when creating or updating component fixtures for screenshot testing, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, and common pitfalls.