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 DevInder1/supply-chain-scanner-public --skill supply-chain-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/supply-chain-scan)<a href="https://agentmods.dev/skills/devinder1/supply-chain-scanner-public/supply-chain-scan"><img src="https://agentmods.dev/badge/skills/devinder1/supply-chain-scanner-public/supply-chain-scan/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/devinder1/supply-chain-scanner-public/supply-chain-scan"><img src="https://agentmods.dev/badge/skills/devinder1/supply-chain-scanner-public/supply-chain-scan.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.00074 | $0.00491 |
| Opus 5 | $0.00037 | $0.00246 |
| Sonnet 5 | $0.00015 | $0.00098 |
| Haiku 4.5 | $0.00007 | $0.00049 |
Grade A, and why
supply-chain-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 9d 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
Supply chain scan
When the user asks about dependency vulnerabilities, CVEs, supply-chain risk, IDE extension security, or wants to audit package.json / lockfiles / requirements.txt:
- Use the tridentchain MCP tools — pick the right scope:
scan_project— fast scan of project deps only (npm, PyPI). Best when the user explicitly says "project only" or wants a fast pre-commit check.scan_full— comprehensive: project deps + Homebrew/apt packages + VS Code + JetBrains extensions. Use when the user says "everything", "system", "machine", "IDE", or asks about extension security.
- Pass
project_pathas the workspace root (absolute path). - Use
output_dir.tridentchain-outunder the project unless the user specifies another path. - Lead the summary with EPSS-prioritised findings — the top 3 by EPSS score are the actual fix-first list. Then summarise by severity. Mention
output_paths.epss_remediation_htmlfor the prioritised view. - If KEV findings are present (
raw_summary.intelligence_sources.sources_used.kev), call them out separately — these are actively exploited in the wild. - No API keys are required for the default profile.
CLI fallback (if MCP unavailable)
tridentchain-security --scan project --project-path <workspace> --output-dir .tridentchain-out
# Or for full system coverage:
tridentchain-security --scan all --project-path <workspace> --output-dir .tridentchain-out
Read .tridentchain-out/scan-report.json for the full data; scan-remediation-epss.html for the prioritised remediation queue.
Do not
- Put API keys in chat; use environment variables only.
- Scan paths outside the user's project without permission.
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.
- 9d ago First seen · 32 lines · 74 tokens per session scan A c78d91204bac
supply-chain-scan is a skill published in the GitHub repository DevInder1/supply-chain-scanner-public (0 stars, last pushed 1mo ago), licensed MIT. It adds 74 tokens to every session and 491 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
bob-egress
List, add, test, enable, disable, or remove Hacker Bob egress profiles from Codex.
bob-export
Create a Hacker Bob post-release improvement bundle for the currently installed Bob version.
analyzing-sbom-for-supply-chain-vulnerabilities
Parses Software Bill of Materials (SBOM) in CycloneDX and SPDX JSON formats to identify supply chain vulnerabilities by correlating components against the NVD CVE database via the NVD 2.0 API. Builds dependency graphs, calculates risk scores, identifies transitive vulnerability paths, and generates compliance reports.…
pipeline-report
A procedure for reporting the state of an amoCRM sales funnel, a set of stages that deals move through before they are won or lost. It groups deals by stage and value and checks how long they have been inactive.
complete-task
A workflow for completing or reassigning ELMA365 business-process tasks. ELMA365 is a business process management system in which tasks move a process from one step to the next.
gigachat-embeddings
A text-embedding workflow for GigaChat. Embeddings are numeric representations that let software compare meanings rather than only matching exact words.