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 tahirraufkeeyu/software-development-agent-stack--sdas --skill dependency-remediationgit clone --depth 1 https://github.com/tahirraufkeeyu/software-development-agent-stack--sdasWrote 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/tahirraufkeeyu/software-development-agent-stack--sdas/dependency-remediation)<a href="https://agentmods.dev/skills/tahirraufkeeyu/software-development-agent-stack--sdas/dependency-remediation"><img src="https://agentmods.dev/badge/skills/tahirraufkeeyu/software-development-agent-stack--sdas/dependency-remediation/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/tahirraufkeeyu/software-development-agent-stack--sdas/dependency-remediation"><img src="https://agentmods.dev/badge/skills/tahirraufkeeyu/software-development-agent-stack--sdas/dependency-remediation.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.00076 | $0.02873 |
| Opus 5 | $0.00038 | $0.01437 |
| Sonnet 5 | $0.00015 | $0.00575 |
| Haiku 4.5 | $0.00008 | $0.00287 |
Grade A, and why
dependency-remediation 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.
How it starts
The opening of the file, as written. The whole thing — 307 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to use
dependency-audithas producedsecurity/findings/dependencies.jsonand at least one finding is High severity or higher.- A Dependabot / Renovate PR has stalled and you need a human-driven remediation pass.
- A vendor advisory (GHSA, CVE, ecosystem-specific) has been published affecting a direct or transitive dependency.
- A release is gated on closing CVEs above a configured severity threshold.
Do not use this skill to scan for vulnerabilities — that's dependency-audit. Do not use it for secret leaks in dependency manifests — that's secret-remediation.
Inputs
security/findings/dependencies.jsonfromdependency-audit, or an equivalent CVE list.- Write access to the repo (to change lockfiles and raise a PR).
- Local environment with the relevant package manager installed (
npm,poetry,go,cargo,mvn). - Optional: access to the SBOM store (e.g.
cyclonedx-cliconfigured to publish).
Outputs
security/remediation/dependencies-<date>.md— per-CVE remediation audit trail.- Updated lockfiles (
package-lock.json,poetry.lock,go.sum,Cargo.lock,pom.xml). - A PR with: CVEs closed, packages changed, test evidence, SBOM delta.
- For
accept-with-mitigation: a documented exception with review date.
Tool dependencies
- Package managers:
npm,yarn,pnpm,poetry,pip-tools,go,cargo,mvn,gradle. - Audit tools (to re-verify):
npm audit,osv-scanner,pip-audit,govulncheck,cargo-audit. cyclonedx-bomorsyftfor SBOM regeneration.jqfor parsing findings JSON.
Procedure
-
Triage findings into one of five buckets. For each finding in
dependencies.json:Bucket Criteria Upgrade direct Package is declared in the manifest + fix version exists. Transitive override Package is a sub-dependency + fix version exists but parent hasn't updated. No patch — replace No fix available + a maintained alternative exists with compatible API. No patch — accept No fix, no alternative. Must justify with compensating control. False positive CVE does not apply to our usage (e.g. server-only CVE in a build-time dep).
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 · 307 lines · 76 tokens per session scan A 70291a665e80
dependency-remediation is a skill published in the GitHub repository tahirraufkeeyu/software-development-agent-stack--sdas (18 stars, last pushed 4mo ago), licensed MIT. It adds 76 tokens to every session and 2,873 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…