Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/the-open-agent/oss-skillsnpx agentmods add skills/the-open-agent/oss-skills/supply-chain-securityWrote 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/the-open-agent/oss-skills/supply-chain-security)<a href="https://agentmods.dev/skills/the-open-agent/oss-skills/supply-chain-security"><img src="https://agentmods.dev/badge/skills/the-open-agent/oss-skills/supply-chain-security/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/the-open-agent/oss-skills/supply-chain-security"><img src="https://agentmods.dev/badge/skills/the-open-agent/oss-skills/supply-chain-security.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00100 | $0.02154 |
| Opus 5 | $0.00050 | $0.01077 |
| Sonnet 5 | $0.00020 | $0.00431 |
| Haiku 4.5 | $0.00010 | $0.00215 |
Grade A, and why
supply-chain-security 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 — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Supply Chain Security
Your project's security posture affects everyone downstream. A popular package is a high-value target precisely because compromising it is cheaper than compromising its users individually.
The realistic threat model
Ranked by observed frequency in actual incidents, not by drama:
- Compromised maintainer account — phishing, credential reuse, no 2FA. The single most common root cause of package compromise.
- Malicious dependency — typosquat, or a legitimate package taken over via a maintainer handoff to a stranger who asked nicely.
- Compromised CI — a workflow with excessive permissions, an unpinned third-party
action,
pull_request_targetexecuting fork code. - Malicious contribution — a subtle backdoor in a PR from a patient contributor who spent months building trust.
- Build-time injection —
postinstallscripts,setup.pyexecuting at install, compromised build servers.
Note what is not at the top: vulnerabilities in your own code. Those matter, but the supply chain is where the leverage is.
Baseline hardening
Do all of these. Together they take an afternoon and remove most of the realistic risk.
Accounts
- Hardware 2FA (WebAuthn) on GitHub and every package registry, for every maintainer. SMS 2FA is not sufficient against the phishing that actually happens.
- Registry publishing via OIDC/trusted publishing instead of long-lived tokens.
- Audit org membership and repo access quarterly. Remove inactive maintainers' publish rights, kindly and explicitly — this is not a demotion, it is hygiene.
Repository
- Branch protection on
main, including for admins. - Signed commits/tags for releases (
git config commit.gpgsign true; Sigstoregitsignavoids GPG key management entirely). - Enable private vulnerability reporting: Settings → Security → "Private vulnerability reporting". This gives researchers a channel that is not a public issue.
- Enable Dependabot alerts, secret scanning, and push protection.
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 · 203 lines · 100 tokens per session scan A 1f901f4f6215
supply-chain-security is a skill published in the GitHub repository the-open-agent/oss-skills (5 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 100 tokens to every session and 2,154 once invoked, about $0.0005 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-31.
Other skills, from other repositories
opentrons-dev-update
Guide users through setting up or updating a local development environment for the Opentrons opentrons/opentrons monorepo. Use this skill whenever a user mentions setting up or updating Opentrons development, cloning the Opentrons repo, installing or refreshing dev dependencies for Opentrons, getting started…
opentrons-dev-setup
Guide users through setting up a local development environment for the Opentrons opentrons/opentrons monorepo. Use this skill whenever a user mentions setting up Opentrons development, cloning the Opentrons repo, installing dev dependencies for Opentrons, getting started contributing to Opentrons, or hits errors…
cn-check
Install and run the Continue CLI (cn) to execute AI agent checks on local code changes. Use when asked to "run checks", "lint with AI", "review my changes with cn", or set up Continue CI locally.
design-taste-frontend
Anti-slop frontend skill for landing pages, portfolios, and redesigns. The agent reads the brief, infers the right design direction, and ships interfaces that do not look templated. Real design systems when applicable, audit-first on redesigns, strict pre-flight check.
image-to-code
Elite website image-to-code skill for Codex. For visually important web tasks, it must first generate the design image(s) itself, deeply analyze them, then implement the website to match them as closely as possible. In Codex, it must prefer large, readable, section-specific images instead of tiny compressed boards…
brandkit
Premium brand-kit image generation skill for creating high-end brand-guidelines boards, logo systems, identity decks, and visual-world presentations. Trained for minimalist, cinematic, editorial, dark-tech, luxury, cultural, security, gaming, developer-tool, and consumer-app brand systems. Optimized for intentional…