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 This-HW/claude-code-kit --skill agent-creatorgit clone --depth 1 https://github.com/This-HW/claude-code-kitWrote 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/this-hw/claude-code-kit/agent-creator)<a href="https://agentmods.dev/skills/this-hw/claude-code-kit/agent-creator"><img src="https://agentmods.dev/badge/skills/this-hw/claude-code-kit/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/this-hw/claude-code-kit/agent-creator"><img src="https://agentmods.dev/badge/skills/this-hw/claude-code-kit/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.00039 | $0.00725 |
| Opus 5.5 | $0.00016 | $0.00290 |
| Sonnet 5.5 | $0.00008 | $0.00145 |
| Haiku 4.5 | $0.00004 | $0.00072 |
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.
What it actually says
Agent Creator
새로운 Claude Code 서브에이전트를 생성하고 최적화합니다.
생성 워크플로우
-
요구사항 수집
- 에이전트의 목적
- 사용 시점 (자동 위임 트리거)
- 필요한 도구
- 파일 수정 필요 여부
-
설정 결정
- 모델 선택 (Opus/Sonnet/Haiku)
- 도구 화이트리스트/블랙리스트
-
파일 생성
- 위치:
plugins/{domain}/agents/{category}/(플러그인 구조 — 디렉토리에서 자동 발견됨, manifest 등록 불필요) - 또는
.claude/agents/(프로젝트 로컬) - 파일명:
agent-name.md
- 위치:
-
검증
- frontmatter 형식 확인 (
name·description·model·maxTurns필수) - 도구 이름 검증
- 금지 필드 미사용 확인:
permissionMode·context_cache·output_schema·next_agents·인라인hooks
- frontmatter 형식 확인 (
모델 선택 가이드
| 작업 유형 | 권장 모델 | 이유 |
|---|---|---|
| 전략/분석/리뷰 | opus |
복잡한 추론 |
| 코드 구현/수정 | sonnet |
균형잡힌 성능 |
| 탐색/검증/단순작업 | haiku |
빠른 실행, 비용 효율 |
출력 형식 (claude-code-kit 플러그인 구조)
---
name: [소문자-하이픈]
description: [역할]. MUST USE when: [트리거 조건].
model: [sonnet|opus|haiku]
effort: [low|medium|high|max]
maxTurns: [20 for implementation, 10 for exploration/review]
tools:
- [도구 목록]
disallowedTools:
- Task
---
[시스템 프롬프트]
에이전트 파일은 plugins/{domain}/agents/{category}/{name}.md에 위치한다.
manifest(plugin.json)에는 agent/skill 레지스트리가 없다 — 디렉토리에서
자동 발견되므로 등록 단계가 없다.
자동 위임 최적화
description에 포함하면 자동 위임 빈도 증가:
- "MUST USE when:"
- "Use PROACTIVELY"
- "Use immediately after"
예제
---
name: test-runner
description: Test execution specialist. MUST USE when: code changes are made and tests need to be run.
model: haiku
effort: low
maxTurns: 10
tools:
- Read
- Bash
- Grep
- Glob
disallowedTools:
- Task
---
You are a test automation expert.
When invoked:
1. Identify changed files
2. Run relevant tests
3. Report results with fix suggestions if failed
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 Changed · -14 lines 58c6ef997a41
- 1mo ago First seen · 113 lines · 39 tokens per session scan A 9e92f30d64b6
agent-creator is a skill published in the GitHub repository This-HW/claude-code-kit (4 stars, last pushed 1mo ago), licensed MIT. It adds 39 tokens to every session and 725 once invoked, about $0.0002 per session on Opus 5.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
code-standards
Prabhdeep (Sonu) Singh's personal coding standards — the house rules and quality bar for how code gets written. INVOKE before writing, generating, refactoring, or reviewing ANY code in ANY language — schemas, endpoints, queries, logging, validation, error handling — even when nobody says "standards" or "style".…
design-tree
Make design decisions as an explicit branching tree — genuine alternatives, decisive rationale, rejected branches preserved. INVOKE PROACTIVELY when planning or designing any implementation approach, or choosing between architectures, libraries, or data models — especially in plan mode. Skip trivial or forced changes…
self-review
Surface the riskiest parts of the current diff so a reviewer knows where to look hardest — one inline pass on small diffs, one cold read on a cheaper model tier with in-session synthesis on substantial ones. INVOKE PROACTIVELY whenever a change is finished and about to be handed off, reviewed, or shipped. It points…
ticket-lifecycle
The ticket-as-control-plane rulebook — the single home for the tracker-operations contract, tracker resolution, the type/priority taxonomy, human-only trigger authorization, derived status, and trust boundaries. INVOKE when reading or writing tickets in a queue-driven flow, resolving a repo's tracker, or deciding…
tdd
Test-driven development — the red-green-refactor discipline for code that's correct by design, not by accident. INVOKE PROACTIVELY whenever writing or changing code, fixing a bug, adding or structuring tests, or choosing what to mock — even when nobody says "TDD" or "tests". (Tests are code held to…
pr-conventions
Author PR descriptions from the right per-change-type template (the repo's own PULLREQUESTTEMPLATE wins), embed issue-tracker links, keep the description current as fixes land, and reply to human and bot review threads. INVOKE when opening or updating a PR or responding to reviewer comments — inside /sonu:ship or…