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-writergit 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-writer)<a href="https://agentmods.dev/skills/ivy00johns/skill-madness/skill-writer"><img src="https://agentmods.dev/badge/skills/ivy00johns/skill-madness/skill-writer/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-writer"><img src="https://agentmods.dev/badge/skills/ivy00johns/skill-madness/skill-writer.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.00083 | $0.02402 |
| Opus 5 | $0.00042 | $0.01201 |
| Sonnet 5 | $0.00017 | $0.00480 |
| Haiku 4.5 | $0.00008 | $0.00240 |
Grade A, and why
skill-writer 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 — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Writer
Generate correctly structured SKILL.md files for the Claude Code skill ecosystem. Every skill follows the same frontmatter convention and directory structure.
When to Use
- Creating a new agent role skill
- Creating a new workflow or meta skill
- Reviewing existing skills for spec compliance
- Adding a role to an orchestrated build
Skill Directory Structure
skill-name/
├── SKILL.md # Required — frontmatter + instructions
└── references/ # Optional — loaded on demand
└── detailed-guide.md
Progressive Disclosure
Skills use three-level loading:
- Metadata (~100 tokens) — name + description, always in context
- SKILL.md body (≤5,000 words; soft warning at 500 lines) — loaded when skill triggers
- References (unlimited) — loaded on demand via explicit reads
Keep SKILL.md bodies concise. Move detailed checklists, templates, and reference tables to references/ with clear pointers.
Creating a New Skill
Step 1: Choose the Skill Type
| Type | Directory | Purpose |
|---|---|---|
| Agent role | roles/{name}/ |
Implementation agent for orchestrated builds |
| Meta skill | meta/{name}/ |
Tools for the skill ecosystem itself |
| Workflow | workflows/{name}/ |
Cross-cutting processes |
| Contract | contracts/{name}/ |
Integration contract management |
| Orchestrator | orchestrator/ |
Lead coordinator (singleton) |
Step 2: Write the Frontmatter
Every SKILL.md starts with YAML frontmatter. See references/frontmatter-spec.md for the complete field reference.
Required fields:
name— kebab-case, max 64 chars.claude-*/anthropic-*prefixes are reserved by Anthropic; use them only as a documented exception when the skill targets the corresponding Anthropic product (e.g.,claude-design-brief).version— semver (start at 1.0.0), top-leveldescription—[What] + [When] + [Capabilities]anatomy (≤200 chars target, 1024 hard ceiling)
The description is the primary trigger mechanism. Write it "pushy" — enumerate contexts where the skill should activate. See references/description-patterns.md for templates and the 3-slot anatomy.
What ships with it
7 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.
- yesterday Changed · +12 lines 3c9e0661e6e8
- 9d ago First seen · 166 lines · 83 tokens per session scan A 5c02efd645cf
skill-writer is a skill published in the GitHub repository ivy00johns/Skill-Madness (11 stars, last pushed yesterday), licensed MIT. It adds 83 tokens to every session and 2,402 once invoked, about $0.0004 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…