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 basher83/agent-auditor --skill agent-creatorgit clone --depth 1 https://github.com/basher83/agent-auditorWrote 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/basher83/agent-auditor/agent-creator)<a href="https://agentmods.dev/skills/basher83/agent-auditor/agent-creator"><img src="https://agentmods.dev/badge/skills/basher83/agent-auditor/agent-creator/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/basher83/agent-auditor/agent-creator"><img src="https://agentmods.dev/badge/skills/basher83/agent-auditor/agent-creator.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.00087 | $0.01336 |
| Opus 5.5 | $0.00035 | $0.00534 |
| Sonnet 5.5 | $0.00017 | $0.00267 |
| Haiku 4.5 | $0.00009 | $0.00134 |
Grade A, and why
agent-creator 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.
This is a copy
100% identical to agent-creator — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Creator
Overview
Creates subagent definitions for Claude Code. Subagents are specialized assistants that Claude can invoke for specific tasks.
When to use: User requests an agent, wants to add specialized subagent to plugin, or needs agent structure guidance.
References: Consult
plugins/meta/claude-docs/skills/official-docs/reference/plugins-reference.md and
plugins/meta/claude-docs/skills/official-docs/reference/sub-agents.md for specifications.
CRITICAL: Two Types of Agents
Claude Code has two distinct agent types with different requirements:
Plugin Agents (plugins/*/agents/)
Purpose: Agents distributed via plugins for team/community use
Required frontmatter fields:
description(required) - What this agent specializes incapabilities(required) - Array of specific capabilities
Location: plugins/<category>/<plugin-name>/agents/agent-name.md
Example:
---
description: Expert code reviewer validating security and quality
capabilities: ["vulnerability detection", "code quality review", "best practices"]
---
User/Project Agents (.claude/agents/)
Purpose: Personal agents for individual workflows
Required frontmatter fields:
name(required) - Agent identifierdescription(required) - When to invoke this agenttools(optional) - Comma-separated tool listmodel(optional) - Model alias (sonnet, opus, haiku)
Location: .claude/agents/agent-name.md or ~/.claude/agents/agent-name.md
Example:
---
name: code-reviewer
description: Expert code review. Use after code changes.
tools: Read, Grep, Glob, Bash
model: sonnet
---
Key difference: User agents have name field and system prompt. Plugin agents have capabilities array and documentation.
Agent Structure Requirements (Plugin Agents)
Every plugin agent MUST include:
- Frontmatter with
descriptionandcapabilitiesarray - Agent title as h1
- Capabilities section explaining what agent does
- When to Use section with invocation criteria
- Context and Examples with concrete scenarios
- Located in
agents/agent-name.mdwithin plugin
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 · 200 lines · 87 tokens per session scan A d8cbfecf0378
agent-creator is a skill published in the GitHub repository basher83/agent-auditor (5 stars, last pushed 7mo ago), licensed MIT. It adds 87 tokens to every session and 1,336 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to agent-creator, differing in 0 lines, and is treated as a copy.
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…
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…
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.