Borrowing it
Nothing to install: this file belongs to mtarcure/claude-vibe-squad. 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/mtarcure/claude-vibe-squad/main/.agents/skills/supply-chain-audit/SKILL.mdgit clone --depth 1 https://github.com/mtarcure/claude-vibe-squadWrote 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/mtarcure/claude-vibe-squad/supply-chain-audit)<a href="https://agentmods.dev/skills/mtarcure/claude-vibe-squad/supply-chain-audit"><img src="https://agentmods.dev/badge/skills/mtarcure/claude-vibe-squad/supply-chain-audit/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/mtarcure/claude-vibe-squad/supply-chain-audit"><img src="https://agentmods.dev/badge/skills/mtarcure/claude-vibe-squad/supply-chain-audit.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.00085 | $0.00516 |
| Opus 5 | $0.00043 | $0.00258 |
| Sonnet 5 | $0.00017 | $0.00103 |
| Haiku 4.5 | $0.00009 | $0.00052 |
Grade A, and why
supply-chain-audit 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 11d 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 — 28 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Supply Chain Audit
Audit everything that enters a build or a release without being written by the project, and everything that can modify the release on its way out.
Steps
- Inventory inputs: package dependencies, base images, downloaded binaries and installers, CI actions and plugins, and build-time code generators.
- Check pinning and integrity for each input — exact versions, lockfile presence, checksum or digest verification, and signature verification where the ecosystem supports it. A floating tag is an unpinned input.
- Audit the CI/CD pipeline as attacker surface: who can trigger a build, what secrets each job can read, whether pull-request builds from forks get privileged tokens, and whether build steps can be influenced by the code they are building.
- Check third-party CI actions specifically — pinned to a commit SHA rather than a mutable tag, and reviewed for the permissions they request.
- Look for typosquat and confusion risk: internal package names resolvable from a public registry, recently-renamed or transferred packages, and single-maintainer packages with sudden ownership changes.
- Verify the release path: who can publish, whether publishing requires review, whether artifacts are signed, and whether the published artifact can be reproduced from the tagged source.
- Check install-time execution — post-install scripts, build hooks, and container entrypoint fetches — as these run with developer or build privilege.
- Trace the provenance chain end to end for at least one artifact, and record every point where the chain relies on trust rather than verification.
- Rank findings by whether they permit silent modification of shipped code; that class outranks everything else here.
Acceptance
- All build inputs are inventoried with their pinning and integrity-verification state.
- CI permissions, fork-build behavior, and third-party action pinning are checked and recorded.
- Dependency-confusion and ownership-change risks are examined for internal names.
- The release path is traced end to end, with every trust-not-verification point named.
- Findings that permit silent modification of shipped artifacts are ranked highest.
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.
- 11d ago First seen · 28 lines · 85 tokens per session scan A 395c4c64dff7
supply-chain-audit is a skill published in the GitHub repository mtarcure/claude-vibe-squad (148 stars, last pushed 2d ago), licensed MIT. It adds 85 tokens to every session and 516 once invoked, about $0.0004 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
gh-find-prs
Survey open Codewhale PRs and triage each for mergeability and disposition against the real landing branch.
contributor-onboarding
Help a new contributor get productive on this checkout - inspect sync state against main, build, run the repository's exact verification gate, and produce a local what's-new digest. Never fetches, pulls, or modifies a dirty tree on its own. Explicit-only.
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
gh-file-issue
Use when filing a new Codewhale GitHub issue: turn a bug or idea into a well-formed, actionable issue with repro, acceptance criteria, labels, and milestone.
gh-treasure-hunt
Hunt the issue/PR queue for highest value-over-risk wins: clean focused community PRs, already-implemented issues to close, safe quick-fixes.
recording
Capture screenshots on registered computers, record on macOS or HarmonyOS, and manage saved captures. Probe capabilities before recording.