Borrowing it
Nothing to install: this file belongs to chainloop-dev/chainloop. 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/chainloop-dev/chainloop/main/.claude/skills/vulnerability-remediation/SKILL.mdgit clone --depth 1 https://github.com/chainloop-dev/chainloopWrote 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/chainloop-dev/chainloop/vulnerability-remediation)<a href="https://agentmods.dev/skills/chainloop-dev/chainloop/vulnerability-remediation"><img src="https://agentmods.dev/badge/skills/chainloop-dev/chainloop/vulnerability-remediation/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/chainloop-dev/chainloop/vulnerability-remediation"><img src="https://agentmods.dev/badge/skills/chainloop-dev/chainloop/vulnerability-remediation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 5 findings, up to high
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 →
- high Supply Chain · line 86 Remote code is downloaded and executed. This bypasses code review and could introduce malicious code.Fix: Avoid downloading and executing remote scripts. Use trusted packages from PyPI/npm. If remote fetch is required, verify checksums and use HTTPS.
- medium MCP Rug Pull · line 97 Docker image references without a specific tag (:latest is implicit) or digest (@sha256:...) can be silently replaced by a malicious image.Fix: Pin the image: image:tag or image@sha256:abc123
- medium MCP Rug Pull · line 99 Docker image references without a specific tag (:latest is implicit) or digest (@sha256:...) can be silently replaced by a malicious image.Fix: Pin the image: image:tag or image@sha256:abc123
- medium MCP Rug Pull · line 104 Docker image references without a specific tag (:latest is implicit) or digest (@sha256:...) can be silently replaced by a malicious image.Fix: Pin the image: image:tag or image@sha256:abc123
- low Tool Misuse · line 99 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00048 | $0.02378 |
| Opus 5.5 | $0.00019 | $0.00951 |
| Sonnet 5.5 | $0.00010 | $0.00476 |
| Haiku 4.5 | $0.00005 | $0.00238 |
Grade A, and why
vulnerability-remediation scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s "https://registry.hub.docker.com/v2/repositories/arigaio/atlas/tags?page_size=20&ordering=last_updated" \ How it starts
The opening of the file, as written. The whole thing — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vulnerability Remediation for chainloop
This skill reviews open vulnerability policy violations recorded in Chainloop for the chainloop project and applies fixes to the affected source files.
Step 1: Find the Latest Project Version
Use list_products_with_versions (no parameters needed — uses the current chainloop org) and locate the Chainloop Community Edition product. Find the chainloop project version entry and note its projectVersionId (UUID).
Step 2: Gather Compliance Results and Evidence in Parallel
Once the projectVersionId is known, make both of these calls at the same time:
Call A — get_frameworks_compliance:
project_version_id: the UUID from Step 1framework_ids:["0ceef195-6900-4166-8407-77eb84954ed3"](chainloop-best-practices)
Call B — list_pieces_of_evidence:
project_name:chainloopproject_version_name: the version name from Step 1 (e.g.v1.77.0)latest:true
Parsing the compliance result (Call A)
The response will be large — parse it programmatically using a Bash subagent:
import json
with open('<tool-result-file>') as f:
raw = json.load(f)
data = json.loads(raw[0]['text'])
for req in data:
if 'vulnerabilit' in req.get('name', '').lower():
status = req.get('status', '')
failed = [e for e in req.get('policyEvaluations', [])
if e.get('status') not in ('PASSED', 'SKIPPED')]
print(f"Requirement: {req['name']} — Status: {status}")
for e in failed:
print(f" FAILED: policy={e['name']} material={e.get('materialName','-')} status={e.get('status','-')}")
This gives you the list of failing material names (e.g. control-plane-migrations-report).
Step 3: Download the SARIF for Each Failing Material
From the list_pieces_of_evidence result (Call B above), find the item whose name matches the failing material name and whose kind is SARIF. Use its digest field directly — no need to decode attestations.
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 · 223 lines · 48 tokens per session scan A 231451a9b233
vulnerability-remediation is a skill published in the GitHub repository chainloop-dev/chainloop (606 stars, last pushed 4d ago), licensed Apache-2.0. It adds 48 tokens to every session and 2,378 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-01.
Other skills, from other repositories
generating-and-analyzing-sboms
Produce and ingest CycloneDX and SPDX SBOMs and correlate them to vulnerability intelligence.
analyzing-sbom-for-supply-chain-vulnerabilities
Parses Software Bill of Materials (SBOM) in CycloneDX and SPDX JSON formats to identify supply chain vulnerabilities by correlating components against the NVD CVE database via the NVD 2.0 API. Builds dependency graphs, calculates risk scores, identifies transitive vulnerability paths, and generates compliance reports.…
analyzing-sbom-for-supply-chain-vulnerabilities
Parses Software Bill of Materials (SBOM) in CycloneDX and SPDX JSON formats to identify supply chain vulnerabilities by correlating components against the NVD CVE database via the NVD 2.0 API. Builds dependency graphs, calculates risk scores, identifies transitive vulnerability paths, and generates compliance reports.…
supply-chain-security-scanner
AI-powered software supply chain security auditing skill for agentic platforms. Performs comprehensive dependency vulnerability scanning across npm, PyPI, Maven, Go modules, Cargo, and container images. Generates SBOMs (Software Bill of Materials) in SPDX and CycloneDX formats using Syft and Grype. Validates license…
analyzing-sbom-for-supply-chain-vulnerabilities
Parses Software Bill of Materials (SBOM) in CycloneDX and SPDX JSON formats to identify supply chain vulnerabilities by correlating components against the NVD CVE database via the NVD 2.0 API. Builds dependency graphs, calculates risk scores, identifies transitive vulnerability paths, and generates compliance reports.…
sbom-syft
Software Bill of Materials (SBOM) generation using Syft for container images, filesystems, and archives. Detects packages across 28+ ecosystems with multi-format output support (CycloneDX, SPDX, syft-json). Enables vulnerability assessment, license compliance, and supply chain security. Use when: (1) Generating SBOMs…