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-explorergit 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-explorer)<a href="https://agentmods.dev/skills/ivy00johns/skill-madness/skill-explorer"><img src="https://agentmods.dev/badge/skills/ivy00johns/skill-madness/skill-explorer.svg" alt="Measured on agentmods" 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.00169 | $0.02426 |
| Opus 5 | $0.00084 | $0.01213 |
| Sonnet 5 | $0.00034 | $0.00485 |
| Haiku 4.5 | $0.00017 | $0.00243 |
Grade A, and why
skill-explorer 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 today.
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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Explorer
The user has accumulated a large toolkit (40+ repo skills plus plugin skills loaded into every session). Names blur together, descriptions overlap, and reaching for the wrong entry point (typically orchestrator) wastes a turn before getting redirected. This skill is the deliberate entry point for "what do I have / which one is right for this".
skill-explorer vs its siblings. Use skill-explorer (this skill) to discover, recall, explain, and route — it names the right skill and stops, leaving you to fire it. Use madness when you want that routing decision acted on — it picks the entry point and launches it (confirming first on anything expensive). Use skill-catalog when you want the authoritative generated inventory/counts of what is installed, not a recall or routing answer. (There is no find-skills skill in this repo; that name belongs to a separately-installed plugin.)
Host awareness. This skill runs on any host that loads skills — Claude Code, Hermes, DeepSeek, and others. The routing table and rules below contain plugin-namespaced refs (superpowers:*, claude-mem:*, claude-obsidian:*, feature-dev:*, frontend-design:*) and Claude Code slash commands that exist only in a Claude Code setup. On any other host, treat those as placeholders: name the closest repo skill that is actually loaded in this session, and say so plainly if none covers it. Never report a plugin skill as available when it isn't.
It answers four kinds of question:
| Mode | Triggered by | Output |
|---|---|---|
| Recall | "what was that skill called", "I forgot the name of the one that..." | The skill name, in code, plus one sentence on what it does |
| Catalog | "what skills do I have", "list all my skills", "show me the toolkit" | Grouped list, one line per skill |
| Explain | "what does X do", "tell me about X", "when should I use X" | Purpose, when it triggers, what it produces, related skills |
| Route | "which skill for Y", "I want to do Z", "what should I use to..." | One recommended skill (in code) + why; alternates only if the request is genuinely ambiguous |
What ships with it
3 files 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.
- today Changed · +2 lines 42cb0815ded3
- 8d ago First seen · 156 lines · 169 tokens per session scan A b2be299c15f6
skill-explorer is a skill published in the GitHub repository ivy00johns/Skill-Madness (11 stars, last pushed today), licensed MIT. It adds 169 tokens to every session and 2,426 once invoked, about $0.0008 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-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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…