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 ivy00johns/Skill-Madness --skill dependency-health-loopgit clone --depth 1 https://github.com/ivy00johns/Skill-MadnessWrote 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/ivy00johns/skill-madness/dependency-health-loop)<a href="https://agentmods.dev/skills/ivy00johns/skill-madness/dependency-health-loop"><img src="https://agentmods.dev/badge/skills/ivy00johns/skill-madness/dependency-health-loop/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/ivy00johns/skill-madness/dependency-health-loop"><img src="https://agentmods.dev/badge/skills/ivy00johns/skill-madness/dependency-health-loop.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.00209 | $0.02862 |
| Opus 5 | $0.00105 | $0.01431 |
| Sonnet 5 | $0.00042 | $0.00572 |
| Haiku 4.5 | $0.00021 | $0.00286 |
Grade A, and why
dependency-health-loop 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 10d 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 — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dependency-health-loop
A configuration of [
loop-controller]. That skill supplies the loop machinery — primitive selection, the full guardrail stack, state externalization. This skill supplies the three things specific to "keep deps healthy": the per-pass recipe (audit → one safe bump → gate → PR), a mechanical proof that combines a security/freshness audit with a green gate after every update, and the HITL boundary that holds majors for a human. Readloop-controllerfor the guardrails; they're inherited, not repeated here.Why
disable-model-invocation: this loop edits the lockfile, commits, and pushes branches on its own, on a clock. It is user-driven — you want to type/loop 30m /dependency-health-loop(or/dependency-health-loop), not have Claude silently start bumping packages because an advisory landed.
The 5-part contract
| Part | This loop |
|---|---|
| trigger | a sprint in flight (deps drifting / new advisories), scheduled via /loop 30m /dependency-health-loop, or an explicit /dependency-health-loop |
| action | ONE pass: run the ecosystem audit → pick one safe update (a security fix first, else one over-stale patch/minor) → apply it → run the whole [fix-until-green] gate → open or update a PR. One bump per pass; re-audit the whole tree after |
| proof | no known vulnerabilities AND no pinned dep stale beyond policy AND the gate exits green — all three observed in the same pass, from the audit report + gate exit codes. Default-FAIL: assume unhealthy until the audit proves otherwise |
| memory | dep-health.md (audit snapshot, the bump→result log, deferred majors + why), the PR branch, the lockfile diff, and git history — durable across the session-scoped /loop fires |
| stop | proof holds (clean audit + in-policy freshness + green gate) OR poll/iteration cap OR no-progress for 3 passes (same advisory unfixable within the reversible boundary) OR budget cap OR an HITL checkpoint is hit (a major bump, or a lockfile-semantics change) |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 201 lines · 209 tokens per session scan A 4e659744f6f2
dependency-health-loop is a skill published in the GitHub repository ivy00johns/Skill-Madness (11 stars, last pushed yesterday), licensed MIT. It adds 209 tokens to every session and 2,862 once invoked, about $0.0010 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…