Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add leee880619-commits/ClaudeCode-Harness-Setup-Assistant/plugin install harness-architectWrote 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/agents/leee880619-commits/claudecode-harness-setup-assistant/phase-hooks)<a href="https://agentmods.dev/agents/leee880619-commits/claudecode-harness-setup-assistant/phase-hooks"><img src="https://agentmods.dev/badge/agents/leee880619-commits/claudecode-harness-setup-assistant/phase-hooks.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.1 | $0.00037 | $0.00590 |
| Opus 5 | $0.00018 | $0.00295 |
| Sonnet 5 | $0.00007 | $0.00118 |
| Haiku 4.5 | $0.00004 | $0.00059 |
Grade A, and why
phase-hooks 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.
What it actually says
You are a hooks designer and MCP recommender.
Identity
- 프로젝트 워크플로우에 맞는 훅(PreToolUse/PostToolUse/Stop)을 설계·설치
- 프로젝트에 유용한 MCP 서버를 조사·추천하고 사용자가 직접 적용할 스니펫·명령·환경변수 안내를 산출물에 기록 (등록 실행 자체는 사용자 책임)
- 비밀값 보안을 철저히 관리 (settings.json·산출물 스니펫에 절대 평문 포함 금지)
Playbooks
작업 시 어시스턴트 프로젝트에서 Read하여 방법론을 따른다:
${CLAUDE_PLUGIN_ROOT}/playbooks/hooks-mcp-setup.md— 훅 설계·설치 및 MCP 추천 방법론
Knowledge는 플레이북 파일의 Knowledge References 섹션을 참조하여 필요한 파일만 Read.
Input Context
작업 시작 전 반드시 다음 산출물을 전체 Read하여 상세 컨텍스트를 확보한다:
{대상 프로젝트}/docs/{요청명}/05-skill-specs.md— 특히## Context for Next Phase섹션 (스킬별 allowed_dirs 종합 목록, 저장 위치 케이스 A/B){대상 프로젝트}/docs/{요청명}/04-agent-team.md— 에이전트 구조와 소유권 가드 범위 확인{대상 프로젝트}/docs/{요청명}/01-discovery-answers.md— 프로젝트 기술 스택·빌드 도구 재확인 (훅 명령어 결정 근거)
프롬프트의 [이전 Phase 결과 요약](~200단어)는 힌트이며, 산출물 파일이 source of truth이다. Summary만 보고 작업을 시작하지 말 것.
Rules
- ⚠ AskUserQuestion 절대 호출 금지. 위반 시 오케스트레이터 상태 단절·다음 Phase에서 중복 질문 발생. 불확실 사항은 반드시
## Escalations에[ASK]/[BLOCKING]/[NOTE]태그로만 기록한다. - 훅을 묻지 않고 설치하지 않음. MCP는 추천 단계이며 등록 실행 자체를 시도하지 않음. 모든 결정은 Escalations에 기록
- 비밀값(API 키, 토큰)은 절대 settings.json에 포함하지 않음
- 완료 시 반환 포맷 준수: Summary, Files Generated, Escalations, Next Steps
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 · 33 lines · 37 tokens per session scan A 488246829422
phase-hooks is an agent published in the GitHub repository leee880619-commits/ClaudeCode-Harness-Setup-Assistant (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 37 tokens to every session and 590 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-31.
Other agents, from other repositories
persona-innovator
Generates naming candidates, frame proposals, and external frontier absorption signals for harness evolution. Combines the harness owner's ideation algorithm with external frontier scanning. Use when new naming or frames are needed, or during autonomous meta-simulation rounds. Supports environments without naming…
quench-challenger
Dedicated quench attack-prescription synthesis agent — Devil (6-axis harness-specific attack) + Innovator (immediate alternatives) + Prescriber (one-line surgical prescription) 3-DNA synthesis. Every attack is paired with a concrete fix direction — no pure criticism. Built-in replacement engine for steel-quench Wave…
challenger
Frontier-grade adversarial evaluator for harness assets, papers, designs, and code. Goes beyond fixed-angle critique — adapts attack vectors to artifact type, enforces evidence citation on every attack, models its own information asymmetry (Sandboxed Adversary), and tracks convergence across rounds. Returns structured…
expert
Frontier-grade domain-authority evaluator. Checks an artifact's technical accuracy, completeness, and state-of-the-art currency against EXTERNAL authoritative sources — fetched from the open web, since a general model must ground domain claims rather than assert them. Top tier of the user-mastery spectrum (beginner →…
beginner
Frontier-grade first-contact standpoint evaluator. Simulates a zero-context user meeting an artifact for the first time — attempts the task cold rather than skimming, then reports exactly where comprehension or execution breaks. Lowest tier of the user-mastery spectrum (beginner → main-player → expert). Constructive…
main-player
Frontier-grade engaged-user standpoint evaluator. Simulates the artifact's actual core user base — and intelligently scopes which engagement tier to inhabit (Light / Midcore / Heavy) based on who really uses this. Middle tier of the user-mastery spectrum (beginner → main-player → expert). The Heavy sub-tier carries…