Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/kimsanguine/hplannpx agentmods add skills/kimsanguine/hplan/handoffWrote 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/kimsanguine/hplan/handoff)<a href="https://agentmods.dev/skills/kimsanguine/hplan/handoff"><img src="https://agentmods.dev/badge/skills/kimsanguine/hplan/handoff.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.00043 | $0.01302 |
| Opus 5 | $0.00022 | $0.00651 |
| Sonnet 5 | $0.00009 | $0.00260 |
| Haiku 4.5 | $0.00004 | $0.00130 |
Grade A, and why
handoff 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Handoff — Build Gate → Downstream Coding Ecosystem
Running for: $ARGUMENTS
Core Goal
- hplan은 단독 도구가 아니라 전처리기. Build Gate가 통과하면 결과물을 spec-kit / kiro / gstack / claude code 어느 곳으로든 export.
- 단일 brief JSON → 4개 생태계 동시 export 가능 (
--target all). - 각 생태계의 네이티브 컨벤션 (spec-kit의
specs/NNN-slug/, Kiro의.kiro/specs/) 그대로 따름. - AI PM Handoff Profile v0는 checkpoint와 decision log를 읽기만 하고 source-owned 상태와 opaque reference만 전달.
- Unconditional approval은 checkpoint
GO와 decision-logbuild, conditional approval은 양쪽CONDITIONAL_GO조합만 허용.
Trigger Gate
Use This Skill When
- Evidence + Product + Build Gate 모두 approved
- COGS sentinel GREEN 또는 CONDITIONAL_GO with mitigations
- 사용자가 명시적으로 "이제 Spec-Kit으로 가자" / "Kiro에서 구현" / "GStack /office-hours로"
- 팀 전체 onboarding — AGENTS.md + CLAUDE.md를 새 repo에 박을 때
Route to Other Skills When
- Build Gate 미통과 → 거꾸로 가서
cogs-sentinel,decision-log확인 - Export 후 spec-kit/kiro 안에서의 개별 task 분해 → 각 생태계 native tool
- Export 후 PRD shape 정교화 →
deliver/prd
Boundary Checks
- ❌
hooks/gate_guard.py가 활성화된 프로젝트에서 Build Gate 미승인 → handoff 호출 차단 (의도된 동작). - ❌ 단일 target만 지정해도 다른 target은 영향 받지 않음 (idempotent per target).
Inputs
python3 hplan/scripts/export_handoff.py brief.json --target all --root .
AI PM Handoff Profile v0를 stdout으로 내보내기:
python3 hplan/scripts/export_growth_handoff.py --root .
검증을 모두 통과한 뒤 저장하려면 --output growth-handoff.json처럼 상대 경로를 사용한다. 결과는 project root의 harness/exports/ai-pm/ 아래에만 생성된다. absolute path, .. traversal, symlink는 거부하며, 기존 안전 출력 파일을 의도적으로 교체할 때만 --force를 함께 사용한다.
{
"product_name": "SocialDraft",
"problem": "1인 마케터가 SNS 게시글당 30-45분을 쓰는데 캠페인 데드라인을 자주 놓친다",
"icp": "주 10건+ SNS 콘텐츠 직접 작성하는 1인 마케터 (현재 범용 AI 챗봇 수동 사용)",
"jtbd": "When 미팅 끝나자마자, I want 액션 + 메일, so I can 같은 날 답신",
"functional_requirements": [...],
"acceptance_criteria": [...],
"cogs_ceiling": "$2.70/paid user/month",
"latency_budget": "p95 < 90초",
"counter_position": "범용 AI 챗봇은 단발성 답변, SocialDraft는 브랜드 톤 학습 + 5개 동시 생성",
"not_build": ["일반 음성 받아쓰기", "CRM first-class"],
"mvp_slice": "Zoom 종료 → 1분 안에 액션 + 메일",
"decision": "build"
}
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.
- 7d ago First seen · 99 lines · 43 tokens per session scan A 58df6f1079c8
handoff is a skill published in the GitHub repository kimsanguine/hplan (2 stars, last pushed 22d ago), licensed MIT. It adds 43 tokens to every session and 1,302 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 skills, from other repositories
codex-setup
Initialize sd0x-dev-flow infrastructure for Codex CLI and other non-Claude agents. Generates AGENTS.md, installs the commit-msg hook, copies runner scripts. The pre-push gate is opt-in via --with-push-gate. Use when setting up a new project or after updating skills.
smart-rebase
Smart partial rebase for squash-merge repositories. Auto-detect which commits to keep/drop when base branch was squash-merged into target. Use when: user says 'rebase', 'partial rebase', 'base already merged', 'smart rebase', or /smart-rebase. Not for: simple git rebase (the developer runs it — Claude never executes…
recap-doc
Post-development recap document generator. Use when: AI/Codex has implemented a feature and the user needs a guided walkthrough of what changed and why, with blind-spot detection and anticipated questions. Not for: Q&A follow-up (use /recap-ask), technical share-out for teammates (use /tech-brief), or generic code…
runbook
Generate and update feature release runbooks from existing docs and codebase. Use when: creating operational runbook, release handbook, deployment checklist, pre-release preparation. Not for: incident response (v2), code review (use codex-code-review), architecture design (use architecture).
test-review
Test coverage review via Codex exec. Use when: reviewing test sufficiency, identifying coverage gaps, test quality audit. Not for: generating tests (use codex-test-gen), code review (use codex-code-review). Output: coverage analysis + gap report.
debug
Interactive debugging workflow with hypothesis-driven probe loop. Use when: unknown bugs, script errors, silent failures, troubleshooting. Not for: known bugs (use bug-fix), GitHub issue analysis (use issue-analyze), code understanding (use code-explore). Output: debug report with probe journal + root cause + fix.