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 MadAppGang/claude-code --skill schemasgit clone --depth 1 https://github.com/MadAppGang/claude-codeWrote 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/madappgang/claude-code/schemas)<a href="https://agentmods.dev/skills/madappgang/claude-code/schemas"><img src="https://agentmods.dev/badge/skills/madappgang/claude-code/schemas/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/madappgang/claude-code/schemas"><img src="https://agentmods.dev/badge/skills/madappgang/claude-code/schemas.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.00024 | $0.01129 |
| Opus 5.5 | $0.00010 | $0.00452 |
| Sonnet 5.5 | $0.00005 | $0.00226 |
| Haiku 4.5 | $0.00002 | $0.00113 |
Grade A, and why
schemas 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 1mo 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
plugin: agentdev updated: 2026-01-20
Frontmatter Schemas
Agent Frontmatter
---
name: agent-name # Required: lowercase-with-hyphens
description: | # Required: detailed with examples
Use this agent when [scenario]. Examples:
(1) "Task description" - launches agent for X
(2) "Task description" - launches agent for Y
(3) "Task description" - launches agent for Z
model: sonnet # Required: sonnet | opus | haiku
color: purple # Optional: purple | cyan | green | orange | blue | red
tools: TaskCreate, TaskUpdate, TaskList, TaskGet, Read, Write # Required: comma-separated, space after comma
skills: skill1, skill2 # Optional: referenced skills
---
Field Reference
| Field | Required | Values | Description |
|---|---|---|---|
name |
Yes | lowercase-with-hyphens |
Agent identifier |
description |
Yes | Multi-line string | 3-5 usage examples |
model |
Yes | sonnet, opus, haiku |
AI model to use |
color |
No | See colors below | Terminal color |
tools |
Yes | Tool list | Available tools |
skills |
No | Skill list | Referenced skills |
Color Guidelines
| Color | Agent Type | Examples |
|---|---|---|
purple |
Planning | architect, api-architect |
green |
Implementation | developer, ui-developer |
cyan |
Review | reviewer, designer |
orange |
Testing | test-architect, tester |
blue |
Utility | cleaner, api-analyst |
red |
Critical/Security | (rarely used) |
Tool Patterns by Agent Type
Orchestrators (Commands):
- Must have:
Task,TaskCreate, TaskUpdate, TaskList, TaskGet,Read,Bash - Often:
AskUserQuestion,Glob,Grep - Never:
Write,Edit
Planners:
- Must have:
TaskCreate, TaskUpdate, TaskList, TaskGet,Read,Write(for docs) - Often:
Glob,Grep,Bash
Implementers:
- Must have:
TaskCreate, TaskUpdate, TaskList, TaskGet,Read,Write,Edit - Often:
Bash,Glob,Grep
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.
- 1mo ago First seen · 145 lines · 24 tokens per session scan A 80de37f43455
schemas is a skill published in the GitHub repository MadAppGang/claude-code (286 stars, last pushed 7mo ago), licensed MIT. It adds 24 tokens to every session and 1,129 once invoked, about $0.0001 per session on Opus 5.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
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…