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 commands/shdsjh123-cpu/claude-code-blog-builder/setupgit clone --depth 1 https://github.com/shdsjh123-cpu/claude-code-blog-builderWrote 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/commands/shdsjh123-cpu/claude-code-blog-builder/setup)<a href="https://agentmods.dev/commands/shdsjh123-cpu/claude-code-blog-builder/setup"><img src="https://agentmods.dev/badge/commands/shdsjh123-cpu/claude-code-blog-builder/setup.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.00024 | $0.00437 |
| Opus 5 | $0.00012 | $0.00218 |
| Sonnet 5 | $0.00005 | $0.00087 |
| Haiku 4.5 | $0.00002 | $0.00044 |
Grade A, and why
setup 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.
What it actually says
/setup — 5분 셋업 인터뷰
이 명령은 처음 레포를 clone한 사용자가 자기 회사에 맞게 시스템을 설정할 수 있도록 인터뷰를 진행합니다.
실행 절차
setup-interviewer서브에이전트를 호출합니다.- 서브에이전트가 Phase 1 인터뷰를 진행 (Q1~Q7, 한 번에 한 질문씩).
- 7개 질문이 모두 끝나면 자동으로:
knowledge/brand-facts.template.md→ 답변으로 치환 →knowledge/brand-facts.md로 저장knowledge/banned-words.json도메인 단어 추가CLAUDE.md회사명 치환
- 다음 단계 추천 (
/setup-tone또는/blog-new).
시작 멘트 (서브에이전트가 출력)
안녕하세요. 블로그 자동화 시스템 셋업을 시작합니다. 5분 정도 걸려요.
Phase 1 — 회사 기본 정보 (7질문)
Phase 2 — 톤 학습 (선택, /setup-tone)
Phase 3 — 도메인 특화 (선택, /setup-domain)
지금은 Phase 1만 진행합니다. 끝나면 바로 첫 글을 쓸 수 있어요.
준비되셨나요? 첫 질문 갑니다.
사전 조건 점검
서브에이전트 호출 전에 아래를 확인:
knowledge/brand-facts.md가 이미 존재하고 placeholder가 아니면 → 사용자에게 "이미 셋업되어 있습니다. 다시 하시겠어요? (이전 데이터 덮어쓰기)" 확인knowledge/brand-facts.template.md가 없으면 → 에러 메시지 + "레포 clone이 완전한지 확인하세요" 안내
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 · 39 lines · 24 tokens per session scan A 2aa747519157
setup is a command published in the GitHub repository shdsjh123-cpu/claude-code-blog-builder (21 stars, last pushed 4mo ago), licensed MIT. It adds 24 tokens to every session and 437 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-30.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.