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 humaisali/Awesome-AI-Skills --skill agent-creatorgit clone --depth 1 https://github.com/humaisali/Awesome-AI-SkillsWrote 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/humaisali/awesome-ai-skills/agent-creator)<a href="https://agentmods.dev/skills/humaisali/awesome-ai-skills/agent-creator"><img src="https://agentmods.dev/badge/skills/humaisali/awesome-ai-skills/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/humaisali/awesome-ai-skills/agent-creator"><img src="https://agentmods.dev/badge/skills/humaisali/awesome-ai-skills/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.00022 | $0.02537 |
| Opus 5 | $0.00011 | $0.01269 |
| Sonnet 5 | $0.00004 | $0.00507 |
| Haiku 4.5 | $0.00002 | $0.00254 |
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 10d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- agent-creator — 89% identical, 18 lines differ
How it starts
The opening of the file, as written. The whole thing — 261 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Creator
A skill for creating custom subagents packaged inside proper plugins. This skill handles the entire flow: gathering requirements, generating a rich persona from even a one-line description, scaffolding the correct folder structure, and optionally creating a companion skill that auto-routes tasks to the new agent.
When to use
Use this skill whenever you need a dedicated, isolated "brain" to handle a specific repetitive task, or when you find yourself repeatedly pasting the same massive system prompt or constraints into the main chat. Creating a dedicated subagent keeps the main conversation lightweight and focused.
Why this exists
Subagents live inside plugins at <appDataDir>\config\plugins\. For
a subagent to be properly registered and invokable, it needs to be inside a
plugin's agents/ directory with a valid plugin.json. Getting this structure
right manually is tedious and error-prone. This skill automates the entire
process so the user can go from "I want an agent that reviews code" to a fully
functional, properly structured subagent in under a minute.
Target directory
All agents are created inside plugins at:
<appDataDir>\config\plugins\<plugin-name>\
If the user wants the agent inside an existing plugin, add the agent folder
to that plugin's agents/ directory. If no plugin is specified, create a new
plugin named <agent-name>-plugin.
Before creating any path, validate both <agent-name> and <plugin-name>:
- accept only lowercase letters, numbers, and single hyphens:
^[a-z0-9]+(-[a-z0-9]+)*$ - reject
/,\,.,.., absolute paths, whitespace, shell metacharacters, and YAML metacharacters - resolve the final target path and verify it stays under
<appDataDir>\config\plugins\ - stop and ask for a safe replacement instead of sanitizing a suspicious name silently
Workflow
Follow these steps in order. Do NOT skip the interview — even a one-line description from the user needs to be expanded into a proper persona.
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.
- 10d ago First seen · 261 lines · 22 tokens per session scan A f77e0879895e
agent-creator is a skill published in the GitHub repository humaisali/Awesome-AI-Skills (5 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 2,537 once invoked, about $0.0001 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-31.
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…