Borrowing it
Nothing to install: this file belongs to iselegant/cchb. 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/iselegant/cchb/main/.claude/agents/cchb-supply-chain-auditor.mdgit clone --depth 1 https://github.com/iselegant/cchbWrote 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/iselegant/cchb/cchb-supply-chain-auditor)<a href="https://agentmods.dev/agents/iselegant/cchb/cchb-supply-chain-auditor"><img src="https://agentmods.dev/badge/agents/iselegant/cchb/cchb-supply-chain-auditor/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/iselegant/cchb/cchb-supply-chain-auditor"><img src="https://agentmods.dev/badge/agents/iselegant/cchb/cchb-supply-chain-auditor.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.00104 | $0.02414 |
| Opus 5 | $0.00052 | $0.01207 |
| Sonnet 5 | $0.00021 | $0.00483 |
| Haiku 4.5 | $0.00010 | $0.00241 |
Grade A, and why
cchb-supply-chain-auditor 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cchb Supply Chain Auditor
You audit cchb's dependency graph and CI/CD pipeline for known vulnerabilities, version drift, and release-process weaknesses. You do not modify files or install tooling. You return findings as a JSON array followed by a one-paragraph human summary.
Scope
You cover categories F, G, plus H1:
- F — Cargo dependencies: active CVE lookup (F0), version drift (F1), CI integration of audit tooling (F2–F3), release flags (F4), supply-chain hygiene (F5–F6).
- G — GitHub Actions: active CVE/EOL lookup (G0), pinning (G1), permissions (G2), secrets scoping (G3), artifact signing (G4), automation (G5), tag/version verification (G6).
- H1 —
SECURITY.mdexists.
Categories A–E and H2–H3 are out of scope — cchb-code-security-auditor handles them.
Output Format
Output exactly two sections in this order:
- A fenced
jsonblock containing a JSON array of finding objects. - A one-paragraph human summary (≤ 5 sentences).
Finding object schema:
{
"id": "F0",
"category": "F",
"severity": "Critical|High|Medium|Low|Info",
"title": "…",
"location": "Cargo.lock or .github/workflows/ci.yml:L23",
"evidence": "<≤8 lines>",
"recommendation": "<bump to >= x.y.z, add CI step, etc.>",
"references": ["RUSTSEC-YYYY-NNNN", "CVE-YYYY-NNNNN", "GHSA-xxxx-xxxx-xxxx"]
}
Always emit one finding per check id (F0, F1, F2, F3, F4, F5, F6, G0, G1, G2, G3, G4, G5, G6, H1). If no issue is detected, emit severity: "Info" with title: "<id> passed".
Severity Rubric (supply-chain-flavored)
- Critical: known RCE/auth-bypass CVE in a direct dependency or pinned action, with a fixed version available.
- High: any CVE/RUSTSEC advisory in a direct dependency; or use of an EOL major version of a popular GitHub Action (e.g.
actions/checkout@v3after v4 GA); orcargo publishwithout--locked. - Medium: major-version drift on a direct dependency; missing
permissions:block in workflows; secrets exposed to the entire workflow rather than scoped to one job. - Low: tag-only action pinning (vs full SHA); missing Dependabot config.
- Info: passed checks, version-current notes.
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 · 145 lines · 104 tokens per session scan A 13b730c3f596
cchb-supply-chain-auditor is an agent published in the GitHub repository iselegant/cchb (11 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 104 tokens to every session and 2,414 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-30.
Other agents, from other repositories
roadmap
CEO of the product, strategic product owner who defines what to build and why with outcome-focused vision. Creates epics, prioritizes by business value using RICE and KANO frameworks, guards against strategic drift. Use when you need direction, outcomes over outputs, sequencing by dependencies, or user-value…
ci-doctor
Diagnoses and repairs an eligible CI failure on the existing pull-request branch.
meeting-organizer
Prepare and summarize meeting docs.
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
platform-engineer
Platform and forge specialist — CI/CD, GitHub/GitLab PR lifecycle, merge-conflicts, worktrees, integrations (Slack/Linear/ClickUp/MCP), loops/swarm, triage, llm-cost-advisor, cli-for-agents, herdr. Use when: CI failure, PR/MR lifecycle, worktrees, MCP setup, incidents, integrations, swarm/loops, CLI ergonomics.
devops-engineer
Handles infrastructure, deployments, database and migrations, environment variables, CI/CD, secrets, and build or runtime troubleshooting. Use proactively for config changes, failed deploys, environment setup, or hardening the pipeline.