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 fix-plangit 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/fix-plan)<a href="https://agentmods.dev/skills/devinder1/supply-chain-scanner-public/fix-plan"><img src="https://agentmods.dev/badge/skills/devinder1/supply-chain-scanner-public/fix-plan/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/fix-plan"><img src="https://agentmods.dev/badge/skills/devinder1/supply-chain-scanner-public/fix-plan.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.00085 | $0.00602 |
| Opus 5.5 | $0.00034 | $0.00241 |
| Sonnet 5.5 | $0.00017 | $0.00120 |
| Haiku 4.5 | $0.00009 | $0.00060 |
Grade A, and why
fix-plan 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 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.
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
Fix plan
When the user asks for a remediation plan, fix recipe, or "what should I patch first":
- Run a scan first (use
scanorscan-fullper scope). If a recent.tridentchain-out/scan-report.jsonexists, you may reuse it. - From
raw_summary.affected_components, build a prioritised plan:- Sort by EPSS score descending — the user wants the actively-exploited ones first.
- For each finding, capture: package name, current version, fix version, ecosystem, CVE IDs, EPSS score, KEV status.
- Present the plan as a table or numbered list. For each line include:
- Risk badge:
URGENTif KEV-listed OR EPSS > 0.5;HIGHif EPSS > 0.1;INFOotherwise. - Semver jump: PATCH (e.g., 5.0.5 → 5.0.6), MINOR (5.0.5 → 5.1.0), or MAJOR (5.x → 6.x). MAJOR bumps need user review.
- Exact command the user can copy-paste:
- npm:
cd <manifest_dir> && npm install <pkg>@<fix_version> - pip:
pip install --upgrade '<pkg>>=<fix_version>' - Homebrew (system):
brew upgrade <pkg>
- npm:
- Risk badge:
- After the plan, suggest the user re-run
validate-fixesonce the patches are applied — this closes the loop and verifies the CVEs are actually resolved.
Important constraints
- Never apply the commands yourself. Present the plan; let the user run it. Auto-applying dependency upgrades is the user's decision.
- Flag MAJOR semver bumps explicitly. They often introduce breaking changes; do not group them with PATCH bumps.
- Group by manifest. If there are multiple
package.jsonfiles or multiplerequirements.txtin the project, separate the commands per directory.
CLI fallback (no MCP)
tridentchain-security --scan project --project-path . --output-dir .tridentchain-out
# Open the EPSS-prioritised remediation report:
open .tridentchain-out/scan-remediation-epss.html
The HTML report already shows the EPSS-ranked remediation queue with per-package fix commands.
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 · 37 lines · 85 tokens per session scan A 13eff7c222a8
fix-plan is a skill published in the GitHub repository DevInder1/supply-chain-scanner-public (0 stars, last pushed 2mo ago), licensed MIT. It adds 85 tokens to every session and 602 once invoked, about $0.0003 per session on Opus 5.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.
recurrent-payment
A recurring-payment workflow for T-Kassa, a payment service. It links a customer's card during an initial payment and later charges that saved payment authorisation for a subscription.
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-image
An image-generation workflow for GigaChat, an AI service that creates pictures from text descriptions. It also supports checking the remaining usage allowance and adding an uploaded reference image.