Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add scholarly360/owasp-top10-web-skills --skill software-supply-chain-failuresgit clone --depth 1 https://github.com/scholarly360/owasp-top10-web-skillsWrote 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/scholarly360/owasp-top10-web-skills/software-supply-chain-failures)<a href="https://agentmods.dev/skills/scholarly360/owasp-top10-web-skills/software-supply-chain-failures"><img src="https://agentmods.dev/badge/skills/scholarly360/owasp-top10-web-skills/software-supply-chain-failures/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/scholarly360/owasp-top10-web-skills/software-supply-chain-failures"><img src="https://agentmods.dev/badge/skills/scholarly360/owasp-top10-web-skills/software-supply-chain-failures.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.00151 | $0.02546 |
| Opus 5.5 | $0.00060 | $0.01018 |
| Sonnet 5.5 | $0.00030 | $0.00509 |
| Haiku 4.5 | $0.00015 | $0.00255 |
Grade A, and why
software-supply-chain-failures 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 2mo 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 — 336 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Software Supply Chain Failures — OWASP A03:2025
Overview
A03:2025 is the #1 community-voted concern and the highest-risk category by exploit score in the entire OWASP Top 10:2025, despite having only 6 CWEs and limited test data:
| Metric | Value |
|---|---|
| OWASP Rank | #3 (new — expands A06:2021 "Vulnerable & Outdated Components") |
| Average Incidence | 5.72% |
| Avg Exploit Score | 8.17 (highest of any category) |
| Avg Impact Score | 5.23 (highest of any category) |
| Key CWEs | CWE-1104, CWE-1395, CWE-1329 |
Key CWEs:
- CWE-1104 — Use of Unmaintained Third-Party Components
- CWE-1395 — Dependency on Vulnerable Third-Party Component
- CWE-1329 — Reliance on Component That is Not Updateable
What This Category Covers
Supply chain failures span the full lifecycle — from sourcing packages to building, distributing, and deploying them:
- Untracked / unmonitored dependencies — direct and transitive
- Vulnerable or unsupported components — unpatched known CVEs
- Absence of SBOM management — no Software Bill of Materials
- Unhardened CI/CD pipelines — no separation of duty, unsigned builds
- Untrusted or typosquatted package sources
- Delayed or absent patching cadence
- Build system compromise (e.g. SolarWinds 2019, Log4Shell 2021, npm worms)
Python-specific surface: Flask alone pulls 7+ transitive packages (Jinja2, Werkzeug, MarkupSafe, itsdangerous, click, blinker, packaging). FastAPI pulls Starlette + Pydantic + their dependencies. Every transitive package is an attack surface.
Detecting Vulnerabilities — Tool Runbook
1. pip-audit (recommended — scans against OSV + PyPI Advisory DB)
# Install
pip install pip-audit
# Scan current environment
pip-audit
# Scan a requirements file
pip-audit -r requirements.txt
# Output JSON for CI
pip-audit -r requirements.txt -f json -o audit-results.json
# Fix automatically where possible
pip-audit --fix
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2mo ago First seen · 336 lines · 151 tokens per session scan A 9d9f27799394
software-supply-chain-failures is a skill published in the GitHub repository scholarly360/owasp-top10-web-skills (22 stars, last pushed 6mo ago), licensed MIT. It adds 151 tokens to every session and 2,546 once invoked, about $0.0006 per session on Opus 5.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
py-clean-arch
Use this skill when the user asks about Clean Architecture in Python — not generic theory, but the specific layer conventions (l1entities, l2usecases, l3interfaceadapters, l4frameworksanddrivers), folder patterns, boundary interfaces, and .importlinter.ini contracts from CJHwong/py-clean-architecture-examples. Fetches…
python-backend
Python backend development expertise for FastAPI, security patterns, database operations, Upstash integrations, and code quality. Use when: (1) Building REST APIs with FastAPI, (2) Implementing JWT/OAuth2 authentication, (3) Setting up SQLAlchemy/async databases, (4) Integrating Redis/Upstash caching, (5) Refactoring…
ty-skills
Python type checking expertise using ty - the extremely fast type checker by Astral. Use when: (1) Adding type annotations to Python code, (2) Fixing type errors reported by ty, (3) Migrating from mypy/pyright to ty, (4) Configuring ty for projects, (5) Understanding advanced type patterns (generics, protocols…
pydantic
Pydantic models and validation. Use when: (1) Defining schemas, (2) Validating input/output, (3) Generating JSON schema.
astropy
Core Python library for astronomy and astrophysics workflows that need Astropy APIs, including units/quantities, coordinates, FITS I/O, tables, time systems, WCS, and cosmology. Use when implementing or debugging astronomical data analysis code with Astropy.
matlab
Builds, reviews, migrates, and plans MATLAB or GNU Octave numerical workflows. Use for arrays, tabular/time data, tests, projects, graphics, MAT files, and explicit Python interoperability.