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/jdforsythe/forge/agent-creatornpx skills add jdforsythe/forge --skill agent-creatorgit clone --depth 1 https://github.com/jdforsythe/forgeWrote 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/jdforsythe/forge/agent-creator)<a href="https://agentmods.dev/skills/jdforsythe/forge/agent-creator"><img src="https://agentmods.dev/badge/skills/jdforsythe/forge/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.00162 | $0.03815 |
| Opus 5 | $0.00081 | $0.01907 |
| Sonnet 5 | $0.00032 | $0.00763 |
| Haiku 4.5 | $0.00016 | $0.00381 |
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 4d 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 — 315 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Creator
Creates structured agent definitions following the 7-component format. Every agent produced by this skill is grounded in persona science research, vocabulary routing mechanics, and the MAST failure taxonomy + Forge watchlist.
Expert Vocabulary Payload
Agent Design: role identity, domain vocabulary payload, deliverables, decision authority, standard operating procedure, anti-pattern watchlist, interaction model, handoff artifact, quality gate Organizational Structure: RACI matrix, task-relevant maturity (Andy Grove), blast radius, reporting lines, escalation path, out-of-scope boundary Security & Risk: STRIDE threat model, OWASP Top 10, attack surface, threat modeling (Shostack) Persona Science: persona alignment, alignment-accuracy tradeoff, role-task fit, persona-length effect, identity token budget Vocabulary Mechanics: vocabulary routing, distributional convergence, register steering, distribution center, 15-year practitioner test, sub-domain clustering, framework attribution
Anti-Pattern Watchlist
Flattery Persona
- Detection: Superlatives and absolutes in role identity — "world-class," "best," "always," "never," "unparalleled," "leading expert."
- Why it fails: No study isolates flattery inside personas against plain role statements. Forge bans superlatives as a style convention: they add tokens, add no scope information, and claim quality instead of defining behavior. Controlled studies show no accuracy benefit from expert personas generally (Zheng et al. 2024, arXiv:2311.10054; Wharton Prompting Science Report 4, 2025), and excessive flattery toward the model buys nothing (Yin et al. 2024, arXiv:2402.14531).
- Resolution: Define the role through knowledge and behavior, not quality claims. Remove every superlative. Describe what the agent knows and does, not how good it is.
Bare Role Label
- Detection: Identity is fewer than 10 tokens with no organizational context. Example: "You are a product manager."
- Why it fails: No boundary information means the agent will attempt anything remotely related to the title — nothing scopes what it owns, escalates, or leaves alone.
- Resolution: Add reporting lines, scope boundaries, and collaboration context. Specify the organizational unit and adjacent roles.
What ships with it
4 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.
- 4d ago First seen · 315 lines · 162 tokens per session scan A aa7f7b291e72
agent-creator is a skill published in the GitHub repository jdforsythe/forge (151 stars, last pushed 2mo ago), licensed MIT. It adds 162 tokens to every session and 3,815 once invoked, about $0.0008 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…