Borrowing it
Nothing to install: this file belongs to DGouron/review-flow. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/DGouron/review-flow/master/.claude/skills/agent-creator/SKILL.mdgit clone --depth 1 https://github.com/DGouron/review-flowWrote 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/dgouron/review-flow/agent-creator)<a href="https://agentmods.dev/skills/dgouron/review-flow/agent-creator"><img src="https://agentmods.dev/badge/skills/dgouron/review-flow/agent-creator.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00048 | $0.01655 |
| Opus 5 | $0.00024 | $0.00827 |
| Sonnet 5 | $0.00010 | $0.00331 |
| Haiku 4.5 | $0.00005 | $0.00166 |
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 7d 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 — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Creator
Activation
This skill activates for:
- Creating a new specialized agent (sub-agent, swarm agent)
- Designing a multi-agent workflow
- Optimizing an existing agent
- Creating a feature-specific or domain-specific agent
Core Principle
A feature-specific agent with a targeted persona always outperforms a generic agent.
❌ "You are a senior backend engineer"
✅ "You are a TDD implementation agent for the ReviewFlow Clean Architecture Fastify/TypeScript project"
Orchestration Architecture
Skill (user entry point, triggers)
→ Agent .claude/agents/*.md (targeted persona, preloaded skills)
→ Skill (knowledge injected into agent context)
| Level | Role | Location |
|---|---|---|
| Skill | Entry point, orchestration | .claude/skills/<name>/SKILL.md |
| Agent | Autonomous execution, dedicated context | .claude/agents/<name>.md |
| Skill (preloaded) | Knowledge injected at startup | skills: in agent YAML |
Agent vs Inline Prompt
| Criteria | Agent .claude/agents/ |
Inline prompt |
|---|---|---|
| Skills preloaded | skills: [tdd, architecture] |
Must read manually |
| Reusable | From any skill | Locked in one skill |
| Configuration | model, maxTurns, permissions, tools, hooks | Limited to Agent tool |
| Discoverability | Visible in .claude/agents/ |
Hidden |
Rule: ALWAYS create .claude/agents/<name>.md. Never inline prompts in references/.
Creation Workflow
Phase 1: INTAKE — Define the need
Before creating the agent, clarify:
- What problem does it solve? — One sentence, not a paragraph
- What is its scope? — Files, modules, or full codebase
- How often will it be used? — One-off or recurring
- Does a skill/agent already cover this? — Check
.claude/skills/AND.claude/agents/ - What is its expected output? — Files created, report, refactoring
- Which existing skills should it know? — For preloading
Phase 2: DESIGN — Create the agent file
What ships with it
3 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.
- 7d ago First seen · 203 lines · 48 tokens per session scan A d571981e7a9f
agent-creator is a skill published in the GitHub repository DGouron/review-flow (42 stars, last pushed 4d ago), licensed MIT. It adds 48 tokens to every session and 1,655 once invoked, about $0.0002 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
community-research-insight
Extract structured insight briefs from community research transcripts or notes. Produces pain points, stakeholder needs, opportunity maps, risks, and follow-up questions. Requires human review before publication.
docs
Use when documentation generally needs to catch up with a branch before pushing or merging, covering internal developer docs, external customer-facing docs, and release notes together — "update the docs", "do a docs pass before I merge", "make sure everything's documented". Prefer this when no single documentation…
install-jazz-github-action
Set up Jazz as a GitHub Action for automated PR code review and on-demand /jazz PR assistance. Use when the user asks to add Jazz to CI, create a GitHub Action workflow, set up PR review automation, enable /jazz commands on PRs, or integrate Jazz with GitHub.
analysis-provenance
Identify code ownership before modifying validators or linters. Checks file headers for provenance indicators, reviews documentation, and determines provenance as UPSTREAM, LOCAL, VENDOR, or UNKNOWN. Prevents accidental modification of upstream tools.
pir-action-tracker
Parses Post-Incident Review (PIR) pages in a Confluence space, fetches live status from referenced Jira tickets, updates action item tables with current status and due dates, marks completed PIRs with a visual closure panel, and surfaces any overdue actions for follow-up. Designed for Customer Success, Support, and…
pull-request-automation
Audits and improves the pull request workflow for a GitHub repository. Covers PR description templates, auto-labelling, CODEOWNERS, PR size checks, and branch protection rules. Invoked when the user asks to improve the PR process, set up PR automation, or add a PR template.