Borrowing it
Nothing to install: this file belongs to verivus-oss/llm-cli-gateway. 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/verivus-oss/llm-cli-gateway/main/.claude/skills/supply-chain-guard/SKILL.mdgit clone --depth 1 https://github.com/verivus-oss/llm-cli-gatewayWrote 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/verivus-oss/llm-cli-gateway/supply-chain-guard)<a href="https://agentmods.dev/skills/verivus-oss/llm-cli-gateway/supply-chain-guard"><img src="https://agentmods.dev/badge/skills/verivus-oss/llm-cli-gateway/supply-chain-guard/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/verivus-oss/llm-cli-gateway/supply-chain-guard"><img src="https://agentmods.dev/badge/skills/verivus-oss/llm-cli-gateway/supply-chain-guard.svg" alt="Reviewed on agentmods" width="80" 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.00139 | $0.01999 |
| Opus 5 | $0.00069 | $0.01000 |
| Sonnet 5 | $0.00028 | $0.00400 |
| Haiku 4.5 | $0.00014 | $0.00200 |
Grade A, and why
supply-chain-guard 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 10d 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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/supply-chain-guard
Canonical process: docs/development/supply-chain-guard/RUNBOOK.md. Read it once
at the start of any session that uses this skill; everything below is a condensed
walkthrough and the runbook is the source of truth. Spec:
docs/plans/supply-chain-guard.draft.md.
The problem this solves
The release gate is blocklist + invariants (npm audit, osv-scanner, the
version blocklist, socket.yml) with no name/instance allowlist, so a new
transitive package with no CVE enters the prod closure silently. This guard adds
the allowlist layer: a committed ledger (supply-chain/prod-closure.ledger.json,
per-name exact acceptedVersions) + instance baseline
(prod-closure.baseline.json), and a scanner that fails the release when the
shipped closure diverges from the reviewed baseline.
Not every drift is equal. A roll-forward (a ledgered name at a new accepted version) is low-risk but still blocks the exit-0 gate until the baseline is refreshed. A tag-along (a name not in the ledger, an unaccepted version, or a name absent from the baseline) needs a real review. Never rubber-stamp a tag-along.
When to invoke
npm run security:audit/ CI failed with[supply-chain-guard] verdict exit 2|3.- You want to sweep drift before cutting a release.
- You want to confirm no new package slipped into the prod tree.
Stages, and your responsibilities
1. Scan
npm run supply-chain:scan # local/advisory (temp-copy fresh resolve; tolerates exit 2)
# or reproduce the gate exactly:
npm run supply-chain:scan:check # --frozen, requires exit 0 (what CI runs)
Read report.md under .supply-chain/scan-<ts>/. Exit 0 clean, 2
roll-forward/dropped, 3 tag-along / source anomaly / integrity mismatch /
reused-invariant failure (forbidden native-tar chain, blocked version,
fetch-in-dist) / P2 license-violation (non-allowlisted or missing SPDX license) /
P2 socket-policy-drift (a socket.yml issueRule changed from its reviewed value),
1 tool error. If clean, stop; otherwise triage every flagged row.
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.
- 10d ago First seen · 158 lines · 139 tokens per session scan A da51b923c941
supply-chain-guard is a skill published in the GitHub repository verivus-oss/llm-cli-gateway (15 stars, last pushed yesterday), licensed MIT. It adds 139 tokens to every session and 1,999 once invoked, about $0.0007 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
provider-integration
Adds new AI providers to claude-council, configures provider API settings, troubleshoots provider connections, and documents the provider script interface. Covers creating provider shell scripts, setting API keys, and validating connectivity. Triggers on "add provider", "new AI agent", "provider not working", "API…
architect
System design, tradeoffs, and complex technical decisions.
security-analyst
Threat-model and find vulnerabilities, with practical remediation.
plan-reviewer
Validate that a work plan is executable before work starts.
researcher
Research external libraries, APIs, and best practices, with evidence.
debugger
Rank root-cause hypotheses and propose the smallest safe fix.