Borrowing it
Nothing to install: this file belongs to snyk/snyk-ls. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/snyk/snyk-ls/main/.cursor/skills/commit/SKILL.mdgit 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/skills/snyk/snyk-ls/commit)<a href="https://agentmods.dev/skills/snyk/snyk-ls/commit"><img src="https://agentmods.dev/badge/skills/snyk/snyk-ls/commit/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/snyk/snyk-ls/commit"><img src="https://agentmods.dev/badge/skills/snyk/snyk-ls/commit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 51 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00057 | $0.01487 |
| Opus 5.5 | $0.00023 | $0.00595 |
| Sonnet 5.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 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 — 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.
- 1mo ago First seen · 261 lines · 57 tokens per session scan A 49f132a51289
commit is a skill published in the GitHub repository snyk/snyk-ls (82 stars, last pushed yesterday), licensed Apache-2.0. It adds 57 tokens to every session and 1,487 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-08-30.
Other skills, from other repositories
add-contributor
Approve a GitHub contributor to open PRs in get-bb/bb, then land the allowlist change with SlopCop and CI skipped. Use for requests such as "add @username to be able to open PRs" or an explicit add-contributor invocation.
bb-cloud-ai
Check, turn off, or troubleshoot bb cloud, the hosted service that writes thread titles and commit messages and transcribes voice input for signed-in bb accounts.
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.
git-commit-craft
Write small, scoped, well-explained git commits instead of one giant dump of unrelated changes.
sync
Commit, fetch/pull, rebase, and push with file-count safety checks. Worktree-aware jj sync. Use when syncing the repository.
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.