agentmods.dev

validate-fixes

validate-fixes is a skill for Claude Code from DevInder1/supply-chain-scanner-public. It costs 72 tokens per session (419 once invoked), scanned A, original, MIT.

A verification workflow for checking whether a dependency upgrade fixed known security flaws. It compares security scan results from before and after the change.

In plain words
What is it for?
Use it after commands such as npm update or pip install -U to scan the project again and compare the reports.
Why use it?
It shows which vulnerabilities were fixed, which remain, and whether the upgrade introduced new ones. This avoids assuming a patch worked without checking.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the tridentchain-security plugin — 7 skills shipped together

not rated 0repo 2mo ago A scan 72 tokens original MIT

Good fit Use it after commands such as npm update or pip install -U to scan the project again and compare the reports.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/devinder1/supply-chain-scanner-public/validate-fixes
View source ↗ DevInder1/supply-chain-scanner-public
Install

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.

Any agent
npx skills add DevInder1/supply-chain-scanner-public --skill validate-fixes
Clone the repo
git clone --depth 1 https://github.com/DevInder1/supply-chain-scanner-public

Made for: Claude Code.

Or install tridentchain-security, the plugin that ships this one along with the rest of its 7 skills.

Wrote 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.

agentmods badge for validate-fixes

README.md
[![agentmods](https://agentmods.dev/badge/skills/devinder1/supply-chain-scanner-public/validate-fixes/github.svg)](https://agentmods.dev/skills/devinder1/supply-chain-scanner-public/validate-fixes)
Your own site
<a href="https://agentmods.dev/skills/devinder1/supply-chain-scanner-public/validate-fixes"><img src="https://agentmods.dev/badge/skills/devinder1/supply-chain-scanner-public/validate-fixes/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.

agentmods 80×15 button for validate-fixes

Your own site · 80×15
<a href="https://agentmods.dev/skills/devinder1/supply-chain-scanner-public/validate-fixes"><img src="https://agentmods.dev/badge/skills/devinder1/supply-chain-scanner-public/validate-fixes.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 72 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 419 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00072 $0.00419
Opus 5.5 $0.00029 $0.00168
Sonnet 5.5 $0.00014 $0.00084
Haiku 4.5 $0.00007 $0.00042

Measured 1mo ago against content hash 133253a5dd42, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

validate-fixes 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.

plugins/tridentchain-security/skills/validate-fixes/SKILL.md · 40 lines

What it actually says

Validate fixes after patch

When the user upgrades dependencies or asks to confirm a fix:

Workflow

  1. Baseline — Run scan_project or scan_full on project_path (MCP) or:

    tridentchain-security --scan project --project-path <path> --output-dir .tridentchain-out

    Save the JSON summary or scan-report.json as baseline if the output dir will be overwritten.

  2. Upgrade — Apply dependency changes (npm update, pip install -U, etc.).

  3. Re-scan — Run the same scan again on the same project_path.

  4. Validate — Use one of:

    • MCP: validate_after_patch with baseline_json and after_patch_json (full tool result strings)
    • CLI: 
      tridentchain-security --validate \
  --baseline-report <baseline.json> \
  --after-report .tridentchain-out/scan-report.json

  5. Report — resolved_count, remaining_count, new_count, validation_passed.

Requirements

  • tridentchain-security>=0.1.1 and tridentchain-mcp for MCP path
  • Pin tridentchain-security==0.1.0 only supports manual JSON comparison (no --validate)

CLI fallback (no MCP)

Run tridentchain-security twice, then --validate with two report paths. See docs/CAPABILITIES.md.

Changes

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.

  1. 1mo ago First seen · 40 lines · 72 tokens per session scan A 133253a5dd42

Subscribe to this mod's changes

validate-fixes is a skill published in the GitHub repository DevInder1/supply-chain-scanner-public (0 stars, last pushed 2mo ago), licensed MIT. It adds 72 tokens to every session and 419 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.

CVEClaude CodeSecurityanthropicmcpmodel-context-protocolnvd
Related

Other skills, from other repositories

bob-egress

List, add, test, enable, disable, or remove Hacker Bob egress profiles from Codex.

vmihalis/hacker-bob · 25 tokens

bob-export

Create a Hacker Bob post-release improvement bundle for the currently installed Bob version.

vmihalis/hacker-bob · 18 tokens

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.

theYahia/WWmcp · 26 tokens

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.

theYahia/WWmcp · 24 tokens

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.

theYahia/WWmcp · 24 tokens

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.

theYahia/WWmcp · 20 tokens