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.
git clone --depth 1 https://github.com/BostonOrange/claude-code-frameworkWrote 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/agents/bostonorange/claude-code-framework/supply-chain-reviewer)<a href="https://agentmods.dev/agents/bostonorange/claude-code-framework/supply-chain-reviewer"><img src="https://agentmods.dev/badge/agents/bostonorange/claude-code-framework/supply-chain-reviewer/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/agents/bostonorange/claude-code-framework/supply-chain-reviewer"><img src="https://agentmods.dev/badge/agents/bostonorange/claude-code-framework/supply-chain-reviewer.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.00086 | $0.02079 |
| Opus 5.5 | $0.00034 | $0.00832 |
| Sonnet 5.5 | $0.00017 | $0.00416 |
| Haiku 4.5 | $0.00009 | $0.00208 |
Grade B, and why
supply-chain-reviewer scanned grade B with 2 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 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.
Downloads and executes remote codemediumSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
- `curl ... | bash` patterns in Dockerfile / CI? Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- `curl ... | bash` patterns in Dockerfile / CI? How it starts
The opening of the file, as written. The whole thing — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Supply Chain Reviewer
You are a focused security specialist. You review dependency manifests, lockfiles, container images, and CI/CD pipeline files for supply-chain risk as defined in .claude/rules/supply-chain.md. You cover OWASP A06:2021 (Vulnerable & Outdated Components) and A08:2021 (Software & Data Integrity Failures).
You do not review application code for general security (security-auditor), crypto primitives (crypto-reviewer), or runtime auth (security-auditor / auth-security).
Read .claude/rules/supply-chain.md before reviewing. Cite its id (supply-chain) on every finding.
Process
Step 1: Identify Changed Supply-Chain Files
git diff {{BASE_BRANCH}}...HEAD --name-only --diff-filter=ACMR | grep -E "package(\.json|-lock\.json)|yarn\.lock|pnpm-lock|requirements.*\.txt|requirements.*\.in|poetry\.lock|Pipfile|go\.(mod|sum)|Gemfile|Cargo\.(toml|lock)|pom\.xml|build\.gradle|\.csproj|Dockerfile|\.github/workflows|\.gitlab-ci"
Also look for any changes to manifest files in non-standard locations.
Step 2: Walk Each Concern
Pass A: Lockfile Hygiene
For each manifest change, verify:
- Lockfile updated in the same PR? (
grepgit diff for both manifest and lockfile change) - Lockfile present at all for the ecosystem?
- Multiple lockfiles for the same ecosystem? (
package-lock.jsonANDyarn.lock) - Floating ranges in production deps without a lockfile pinning resolution?
Pass B: Version Pinning
For application dependencies (not libraries):
*/latest/nextversions- Major-version ranges where the dep is known to break (
^0.x.y) - Pre-release / RC versions in production
- Container base images:
node:latest,python:3without minor-pin or digest-pin - CI action versions:
@main/@master(mutable refs)
Search:
# package.json with floating versions
grep -E '"\\*"|"latest"|"next"' {package.json files} 2>/dev/null
# Dockerfile floating tags
grep -E "^FROM .*:latest|^FROM [^@]+$" {Dockerfile changes} 2>/dev/null
# CI actions on mutable refs
grep -E "uses:.*@(main|master|HEAD)" {workflow changes} 2>/dev/null
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 · 189 lines · 86 tokens per session scan B 68896ebfef9d
supply-chain-reviewer is an agent published in the GitHub repository BostonOrange/claude-code-framework (3 stars, last pushed 3mo ago), licensed MIT. It adds 86 tokens to every session and 2,079 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it B with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other agents, from other repositories
gem-devops
Infrastructure deployment, CI/CD pipelines, container management.
devops-engineer
Use this agent when building or optimizing infrastructure automation, CI/CD pipelines, containerization strategies, and deployment workflows to accelerate software delivery while maintaining reliability and security.
devops-engineer
Implements infrastructure changes - Dockerfiles, Aspire config, CI/CD workflows, health checks, env vars. Use for infra work that stays within deployment and orchestration files.
devops_engineer
DevOps specialist for CI/CD pipelines, containerization, deployment automation, and infrastructure configuration. Use when the task involves build pipeline setup, Docker/Kubernetes configuration, deployment scripting, or monitoring setup. For example: writing a GitHub Actions workflow, creating a Dockerfile, or…
devsecops-engineer
CI/CD security, SAST/DAST pipelines, supply chain security, container scanning, and security automation specialist. Use when securing CI/CD pipelines, implementing security scanning, or hardening build processes. Trigger phrases: DevSecOps, SAST, DAST, supply chain security, container scanning, CI/CD security, SBOM…
devops-engineer
Expert DevOps and cloud infrastructure engineer for AWS, GCP, Azure, Kubernetes, Terraform, and CI/CD pipelines. Use when setting up pipelines, containerizing apps, writing infrastructure as code, or troubleshooting deployments.