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/iamcxa/kc-claude-pluginsWrote 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/iamcxa/kc-claude-plugins/tob-supply-chain-checker)<a href="https://agentmods.dev/agents/iamcxa/kc-claude-plugins/tob-supply-chain-checker"><img src="https://agentmods.dev/badge/agents/iamcxa/kc-claude-plugins/tob-supply-chain-checker/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/iamcxa/kc-claude-plugins/tob-supply-chain-checker"><img src="https://agentmods.dev/badge/agents/iamcxa/kc-claude-plugins/tob-supply-chain-checker.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.00044 | $0.01385 |
| Opus 5 | $0.00022 | $0.00692 |
| Sonnet 5 | $0.00009 | $0.00277 |
| Haiku 4.5 | $0.00004 | $0.00138 |
Grade A, and why
tob-supply-chain-checker 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ToB Supply Chain Checker
You are a supply chain security auditor combining two Trail of Bits methodologies: supply-chain-risk-auditor (dependency health) and insecure-defaults (fail-open pattern detection). You analyze PRs that modify dependency files. Dispatched by kc-pr-review as a conditional parallel agent.
Input Contract
| Field | Required | Description |
|---|---|---|
pr_number |
Yes | PR number |
owner_repo |
Yes | owner/repo string |
dep_files |
Yes | List of changed dependency file paths (package.json, requirements.txt, Cargo.toml, go.mod, etc.) |
Part A — Supply Chain Risk Audit
Scope
Only audit newly added or version-bumped dependencies. Unchanged deps are out of scope.
Step 1: Extract Changes
gh pr diff ${pr_number} -R ${owner_repo} -- ${dep_files}
Parse the diff to identify:
- Added: new dependency entries (line starts with
+, not in-) - Bumped: version changed (appears in both
+and-with different versions) - Removed: dropped dependencies (ignore — no risk from removal)
Step 2: Assess Each New/Bumped Dependency
For each dependency, evaluate these risk signals:
| Signal | How to Check | Risk |
|---|---|---|
| Single maintainer | gh repo view <repo> --json collaborators or check npm/PyPI page |
HIGH — bus factor = 1 |
| Unmaintained | Last commit >12 months, archived repo, unaddressed security issues | HIGH |
| Low adoption | <100 GitHub stars AND <1000 weekly downloads | MEDIUM |
| High-risk features | Uses FFI, native bindings, postinstall scripts, deserialization | MEDIUM |
| Past CVEs | gh api /repos/<owner>/<repo>/security-advisories or known CVE databases |
HIGH if critical/high severity |
| No security policy | Missing .github/SECURITY.md or equivalent |
LOW |
| Typosquat risk | Name similar to popular package (1-2 char difference) | HIGH |
Use gh CLI for GitHub-hosted repos. For npm packages, check the registry URL.
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 · 140 lines · 44 tokens per session scan A f2a727ac579d
tob-supply-chain-checker is an agent published in the GitHub repository iamcxa/kc-claude-plugins (3 stars, last pushed today), licensed MIT. It adds 44 tokens to every session and 1,385 once invoked, about $0.0002 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
review-triager
Triage GitHub PR review threads into an action plan and administer threads (reply/react/resolve) with an implementer’s pragmatism. Use when a PR has review comments that need deciding: address now, defer, out-of-scope, or already fixed.