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 agentmods add skills/devinder1/supply-chain-scanner-public/scannpx skills add DevInder1/supply-chain-scanner-public --skill scangit clone --depth 1 https://github.com/DevInder1/supply-chain-scanner-publicWrote 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/devinder1/supply-chain-scanner-public/scan)<a href="https://agentmods.dev/skills/devinder1/supply-chain-scanner-public/scan"><img src="https://agentmods.dev/badge/skills/devinder1/supply-chain-scanner-public/scan.svg" alt="Measured on agentmods" 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.00079 | $0.00456 |
| Opus 5 | $0.00039 | $0.00228 |
| Sonnet 5 | $0.00016 | $0.00091 |
| Haiku 4.5 | $0.00008 | $0.00046 |
Grade A, and why
scan 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 5d 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.
What it actually says
Project scan
When the user asks to scan a project for vulnerabilities, audit package.json / requirements.txt, or check dependency security:
- Call the tridentchain MCP tool
scan_projectwith:project_path= workspace root (absolute path)output_dir=.tridentchain-outrun_profile="full"(live advisory fetch — default)max_findings= 50
- Lead with EPSS-prioritised findings. Pull the top-5 by EPSS score from
raw_summary.affected_components, ranked byepss_score. These are the actual fix-first list. - Then summarise severity totals (critical / high / medium / low).
- If any finding is in the CISA KEV catalog (
source: "kev"), tag it clearly — these are actively exploited in the wild. - Point the user at
output_paths.epss_remediation_htmlfor the prioritised remediation queue (with copy-paste fix commands).
When to use scan vs siblings
| Situation | Use |
|---|---|
| User wants project deps only, live data | scan (this) |
| User is in a hurry / offline | quick-scan |
| User says "system", "IDE", "extensions", "machine", "everything" | scan-full |
| User upgraded packages and wants to verify | validate-fixes |
| User wants to drill into ONE package | why |
| User wants a fix recipe | fix-plan |
CLI fallback
tridentchain-security --scan project --project-path . --output-dir .tridentchain-out
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.
- 5d ago First seen · 35 lines · 79 tokens per session scan A ce60fa2e0b12
scan is a skill published in the GitHub repository DevInder1/supply-chain-scanner-public (0 stars, last pushed 1mo ago), licensed MIT. It adds 79 tokens to every session and 456 once invoked, about $0.0004 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
vulnerability-db
A practical guide for AI agents that need to use vdb. If you are changing the code rather than using it, read AGENTS.md instead.
bob-evaluate-runner
Hacker Bob orchestrator runtime — invoked by /bob-evaluate. Do not call directly.
bob-diff-review
Headless Bob diff-review pipeline — invoked by bob-runner.ts via 'claude --dangerously-skip-permissions --print "/bob-diff-review -- ..."'. Ingests a unified diff, initializes a Bob repo session, builds the symbol surface index, maps changed hunks to impacted surfaces, spawns per-surface evaluator agents, and…
bob-debug
Debug a completed or stuck Hacker Bob session — pipeline quality, drift, failures, improvements.
bob-status
Read Hacker Bob session state, wave status, findings, verification, and grade summaries.
bob-update
Check for Hacker Bob package updates and guide project-local update installation from Codex.