Install any skill in seconds. Free to start, no credit card required.
Get Started Free →ccch1mneyyy/vuln-check
Use when asked to check for security vulnerabilities, or when the /vuln-check command runs — scan the project for known vulnerable dependencies and security anti-patterns.
6 of 24 test cases passed with the skill.
Tokens, turns and time describe resource use, not a dollar price.
Lift withheld: 6 comparable cases; this report requires 8.
A test case the skill fixed. Same model, same prompt, with and without the skill.
When reporting a package advisory found in `pnpm-lock.yaml`, what specific package version metadata fields should be documented in the vulnerability report?
| Checked | Without skill | With skill |
|---|---|---|
| The response records the resolved package version and advisory identifier in dependency findings. | Missed | Passed |
| The response records the affected version range and verified fixed version in dependency findings. | Missed | Passed |
The instructions your model reads when the skill loads.
Assess the requested security surface with evidence. A check returns findings; implement remediation when the user has requested it.
package.json and pnpm-lock.yaml for the affected dependency paths. Use current advisory data, such as pnpm audit, and record the resolved version, advisory, affected range, and verified fixed version where available. Distinguish a dependency advisory match from a demonstrated exploit path in this project.Report potential secrets only by path, line, and type, never their value or a source excerpt. Do not run automatic dependency fixes as part of a check; for requested remediation, make targeted changes and validate the affected paths.
test cases passed with the skill
More skills from the same source and nearby in the registry, with their headline benchmark lift.