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-improvement-plangit 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-improvement-plan)<a href="https://agentmods.dev/skills/ivy00johns/skill-madness/skill-improvement-plan"><img src="https://agentmods.dev/badge/skills/ivy00johns/skill-madness/skill-improvement-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/ivy00johns/skill-madness/skill-improvement-plan"><img src="https://agentmods.dev/badge/skills/ivy00johns/skill-madness/skill-improvement-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.00111 | $0.01296 |
| Opus 5 | $0.00056 | $0.00648 |
| Sonnet 5 | $0.00022 | $0.00259 |
| Haiku 4.5 | $0.00011 | $0.00130 |
Grade A, and why
skill-improvement-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 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 Improvement Plan
Take feedback from skill-deep-review, skill-audit, or manual observations and produce a structured, prioritized plan of specific changes to make.
When to Use
- After a deep review report identifies issues in a skill
- After an audit report surfaces ecosystem-wide problems
- When you have scattered feedback notes and need to organize them into an actionable plan
- When deciding what order to fix things in
Inputs
- Review source — one or more of:
- A deep-review report (markdown from skill-deep-review)
- An audit report (markdown from skill-audit)
- Manual feedback (user-provided notes, conversation context)
- Constraints (optional) — time budget, which skills are off-limits, what to prioritize
Process
Step 1: Parse the Feedback
Read all review/audit reports provided. Extract:
- Every issue with its severity, affected skill, and dimension
- Every recommendation
- Trigger testing results (if from deep-review)
- Coverage gaps (if from audit)
Step 2: Deduplicate and Categorize
Group issues by type:
| Category | Examples |
|---|---|
| Frontmatter fixes | Missing fields, wrong types, bad version |
| Description rewrites | Vague triggers, missing keywords, too long/short |
| Content restructuring | Body too long, needs reference extraction, missing sections |
| Instruction improvements | Ambiguous steps, missing rationale, wrong voice |
| Ownership fixes | Overlaps, missing declarations, stale composes_with |
| New content | Missing reference files, missing examples, missing checklists |
| Deletions | Duplicate content, orphan files, dead links |
Merge duplicates — if the audit and a deep review both flag the same issue, combine them.
Step 3: Prioritize
Score each change on two axes:
- Impact (1–3): How much does fixing this improve the skill ecosystem?
- 3 = Skill doesn't trigger or produces wrong output without this fix
- 2 = Skill works but quality or consistency suffers
- 1 = Polish, nice-to-have
- Effort (1–3): How hard is the change?
- 1 = Quick edit (fix a field, add a line)
- 2 = Moderate rewrite (restructure a section, write a new reference file)
- 3 = Major rework (rewrite a skill from scratch, resolve complex ownership conflicts)
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 · 111 tokens per session scan A cd1e6dca4e81
skill-improvement-plan is a skill published in the GitHub repository ivy00johns/Skill-Madness (11 stars, last pushed 2d ago), licensed MIT. It adds 111 tokens to every session and 1,296 once invoked, about $0.0006 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…