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 skill-updatergit 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/skill-updater)<a href="https://agentmods.dev/skills/ivy00johns/skill-madness/skill-updater"><img src="https://agentmods.dev/badge/skills/ivy00johns/skill-madness/skill-updater/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/skill-updater"><img src="https://agentmods.dev/badge/skills/ivy00johns/skill-madness/skill-updater.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.00107 | $0.01270 |
| Opus 5 | $0.00053 | $0.00635 |
| Sonnet 5 | $0.00021 | $0.00254 |
| Haiku 4.5 | $0.00011 | $0.00127 |
Grade A, and why
skill-updater 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Updater
Execute skill improvement plans by making specific edits to skill files, validating the changes, and prompting the user to sync.
When to Use
- After skill-improvement-plan generates a plan and the user says "go"
- When you have a clear list of edits to make across skills
- When applying fixes from a review report directly (skipping the planning step for simple fixes)
Inputs
- Improvement plan — a structured plan from skill-improvement-plan, OR a list of specific changes to make
- Scope (optional) — which priority levels to execute (e.g., "just P0", "P0 and P1", "all")
Process
Step 1: Parse the Plan
Read the improvement plan. Extract the ordered list of changes with:
- Target skill and file path
- What to change
- The specific edit (old text → new text, new content, file to create/delete)
If the user provided ad-hoc changes instead of a formal plan, organize them into the same structure.
Step 2: Validate Before Editing
For each change, before applying:
- Read the target file — confirm it exists and the content matches expectations
- Check for conflicts — if multiple changes target the same file, plan the edit order to avoid conflicts
- Verify ownership — if changing
ownsfields, check against other skills for overlaps
If anything doesn't match expectations (file content changed since the review, file doesn't exist), flag it and ask the user before proceeding.
Step 3: Apply Changes
Execute changes in priority order (P0 first, then P1, etc.):
For frontmatter edits:
- Use Edit tool to modify specific frontmatter fields
- Preserve YAML formatting and field order
For description rewrites:
- Replace the entire description field with the new text from the plan
- Verify the new description follows the patterns (action verb, trigger contexts)
For content restructuring:
- If moving content to a new reference file: create the reference file first, then edit the body to add the pointer and remove the moved content
- If merging sections: read both sources, combine, write the merged version
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 · 142 lines · 107 tokens per session scan A 613817127eea
skill-updater is a skill published in the GitHub repository ivy00johns/Skill-Madness (11 stars, last pushed 2d ago), licensed MIT. It adds 107 tokens to every session and 1,270 once invoked, about $0.0005 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…