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 madnessgit 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/madness)<a href="https://agentmods.dev/skills/ivy00johns/skill-madness/madness"><img src="https://agentmods.dev/badge/skills/ivy00johns/skill-madness/madness/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/madness"><img src="https://agentmods.dev/badge/skills/ivy00johns/skill-madness/madness.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.00219 | $0.03643 |
| Opus 5 | $0.00110 | $0.01821 |
| Sonnet 5 | $0.00044 | $0.00729 |
| Haiku 4.5 | $0.00022 | $0.00364 |
Grade A, and why
madness 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 yesterday.
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 — 251 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Madness — the front door
This is the one entry point you can reach for when you don't want to think about
which of the dozens of skills is the right one. You say what you're trying to do;
madness figures out the correct starting skill, confirms if it's about to
launch something heavy, and hands you off into it.
Why this exists
The toolkit under-triggers. With dozens of skills loaded every session,
descriptions blur and the model often answers a request directly instead of
reaching for the skill that would do it better. The usual workaround is to type
orchestrator as a panic button — but orchestrator is a multi-agent build
entry point (contracts, role agents, QA gates). On anything that isn't a
parallel build it either spins up machinery you don't need or bounces you with
"this isn't a multi-agent build." So the crutch works, but it's the wrong shape.
madness is the right-shaped crutch: a hair-trigger router whose only job is to
land you in the correct front door and get out of the way. Type /madness, or
ask "where do I even start with this," and it routes.
The prime directive: route, then hand off
Pick the right starting skill, launch it, and stop. madness is not a
meta-orchestrator and must never become the work. It does not write the code,
draft the plan, or run the loop itself — it identifies which skill does that and
invokes it. The moment the target skill is running, madness is done. If you
find yourself doing the task instead of dispatching it, you've drifted; route and
hand off.
This is the deliberate counterpart to skill-explorer, which names a skill but
will not invoke it. madness is the active version: it names and launches.
See "madness vs skill-explorer" below for when to use which.
How a dispatch goes
- Get the intent. If invoked as
/madness <task>, the argument is the intent. If invoked bare (/madnesswith nothing after it), or the intent is too vague to route confidently, show the menu (below) and ask — one question, then route. Don't guess at a heavy route from a one-word prompt.
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.
- yesterday Changed · +13 lines 82afd844612e
- 9d ago First seen · 238 lines · 219 tokens per session scan A 0532b6d76042
madness is a skill published in the GitHub repository ivy00johns/Skill-Madness (11 stars, last pushed today), licensed MIT. It adds 219 tokens to every session and 3,643 once invoked, about $0.0011 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…
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…