Borrowing it
Nothing to install: this file belongs to stacklok/toolhive-studio. 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/stacklok/toolhive-studio/main/.claude/skills/security-vuln-remediation/SKILL.mdgit clone --depth 1 https://github.com/stacklok/toolhive-studioWrote 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/stacklok/toolhive-studio/security-vuln-remediation)<a href="https://agentmods.dev/skills/stacklok/toolhive-studio/security-vuln-remediation"><img src="https://agentmods.dev/badge/skills/stacklok/toolhive-studio/security-vuln-remediation.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00050 | $0.02302 |
| Opus 5 | $0.00025 | $0.01151 |
| Sonnet 5 | $0.00010 | $0.00460 |
| Haiku 4.5 | $0.00005 | $0.00230 |
Grade A, and why
security-vuln-remediation 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 8d 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 — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Vulnerability Remediation
Playbook for analyzing and remediating security vulnerabilities in this Electron/Node.js project. Applies to both CI (Cursor agent in GitHub Actions) and local development.
Project Context
- Package manager: pnpm 11 (lockfile:
pnpm-lock.yaml) - Scanner: Grype with config at
.grype.yaml(only reports vulnerabilities with a fix available) - Audit:
pnpm audit --prod --audit-level=moderate - Existing overrides:
overridesblock inpnpm-workspace.yaml— used to pin transitive dependencies to patched versions (pnpm 11 no longer reads thepnpmfield frompackage.json) - Production deps: listed under
dependenciesinpackage.json - Dev-only deps: listed under
devDependenciesinpackage.json— not shipped to users
Remediation Workflow
Follow these steps in order. Stop at the first step that resolves the vulnerability.
Step 1 — Identify Vulnerabilities
Run both scanners and capture the output:
grype . --config .grype.yaml
pnpm audit --prod --audit-level=moderate
For each finding, record:
- CVE ID (e.g.
CVE-2024-12345) - Affected package and installed version
- Fixed version (if available)
- Severity (critical / high / medium)
- Whether the package is a direct or transitive dependency
Step 2 — Trace the Dependency
For each vulnerable package, understand who pulls it in:
pnpm why <package-name>
Record:
- Which direct dependency depends on it
- How many versions of the package are installed
- Whether it appears under
dependencies(production) ordevDependencies(dev-only)
Step 3 — Attempt an Upgrade
Check if a patch/minor upgrade of the direct dependency resolves the CVE:
pnpm update <direct-dependency>
Or, if the vulnerable package is a direct dependency itself, update its version range in package.json.
After the change:
- Run
pnpm installto regenerate the lockfile - Re-run
grype . --config .grype.yamlto verify the vulnerability is gone
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.
- 8d ago First seen · 215 lines · 50 tokens per session scan A 042669eb96e4
security-vuln-remediation is a skill published in the GitHub repository stacklok/toolhive-studio (163 stars, last pushed today), licensed Apache-2.0. It adds 50 tokens to every session and 2,302 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
agentcore-investigation
Investigate Bedrock AgentCore runtime sessions via CloudWatch Logs Insights — resolve session/trace IDs, query OTEL spans, filter noise, build timelines. Use when debugging AgentCore agent sessions, tracing tool calls, or analyzing latency.
amazon aurora dsql
Deprecated compatibility redirect for Aurora DSQL guidance. Use when a request concerns DSQL, Aurora DSQL, distributed SQL, DSQL schemas, migrations, queries, authentication, performance, or application development.
requirements-authoring
To author, update, and validate functional/non-functional requirements as atomic units with user approval.
coding-agents-hooks-authoring
To author, register, and test Rosetta hooks, add a SemanticKind, or debug a hook that won't fire.
specflow-use
To connect Rosetta with Grid Dynamics SpecFlow MCP; only when SpecFlow is mentioned and the MCP is installed.
qa-knowledge
To run QA engineering — requirements/gap analysis, scenario & spec design, test implementation, failure triage — over the QA knowledge base.