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 agentmods add skills/hashlips/agent-skills/agent-creatornpx skills add HashLips/agent-skills --skill agent-creatorgit clone --depth 1 https://github.com/HashLips/agent-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/hashlips/agent-skills/agent-creator)<a href="https://agentmods.dev/skills/hashlips/agent-skills/agent-creator"><img src="https://agentmods.dev/badge/skills/hashlips/agent-skills/agent-creator.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 | $0.00076 | $0.00738 |
| Opus 5 | $0.00038 | $0.00369 |
| Sonnet 5 | $0.00015 | $0.00148 |
| Haiku 4.5 | $0.00008 | $0.00074 |
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 5d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Creator
Summary
- Build role-driven agent files that are portable and scannable.
- Keep agents concise while preserving operational clarity.
- Require explicit completion and handoff behavior in every agent.
Core Workflow
- Name the file in kebab-case using
<role>-agent.md. - Fill Identity as one paragraph from the template.
- Add role summary only if Identity is not enough.
- Add responsibilities, decision framework, constraints, outputs, and collaboration.
- Add required
Failure modes and recoverymicro-section. - Add required
Completion and handoffsection. - Add optional sections only when they add signal.
- Run compression pass (dedupe, shorten, reference reusable detail).
- Run hard QA gate before delivery.
- Apply final formatting pass using the available MD Design System skill.
Non-Negotiable Rules
- File name — Must be
<descriptor>-agent.md. - Required sections — Responsibilities, decision framework, constraints, failure modes, outputs, collaboration, completion and handoff.
- Completion contract — Must include DoD, stop condition, next role + package, and start rule.
- Identity format — Single paragraph only.
- Readable Markdown — Minimal bold; list-first; no emphasis noise.
- Brevity target — Roughly 250-500 words per agent.
- Portability — No mandatory repo-local paths.
- Skill boundary — Agent defines role behavior; separate skills define reusable procedures.
- Final formatter — Before final output, run generated files through the local MD design system formatter.
Output Contract
- Agent file is usable as-is in system instructions.
- Reader can quickly identify boundaries, outputs, and handoff rules.
- Next role can start from the handoff package without ambiguity.
Reference Index
- Completion and handoff requirements: references/completion-and-handoff.md
- Agent template and section order: references/agent-file-template.md
- Naming and layout rules: references/naming-and-layout.md
- Authoring process and review flow: references/authoring-workflow.md
- Hard pass/fail QA gate: references/qa-rubric.md
- Failure-mode section patterns: references/failure-modes.md
- Role-family compact exemplars: references/role-family-exemplars.md
- Role vs persona distinction: references/role-vs-persona.md
- Collaboration patterns: references/collaboration-patterns.md
- Final Markdown formatting contract: available MD Design System skill
What ships with it
9 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.
- references/agent-file-template.md 1.6 KB
- references/authoring-workflow.md 1.1 KB
- references/collaboration-patterns.md 734 B
- references/completion-and-handoff.md 773 B
- references/failure-modes.md 643 B
- references/naming-and-layout.md 693 B
- references/qa-rubric.md 554 B
- references/role-family-exemplars.md 1.4 KB
- references/role-vs-persona.md 689 B
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.
- 5d ago First seen · 63 lines · 76 tokens per session scan A 99fac652d7dc
agent-creator is a skill published in the GitHub repository HashLips/agent-skills (24 stars, last pushed 10d ago), licensed MIT. It adds 76 tokens to every session and 738 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…