Borrowing it
Nothing to install: this file belongs to Chachamaru127/codex-harness. 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/Chachamaru127/codex-harness/main/.codex/skills/handoff/SKILL.mdgit clone --depth 1 https://github.com/Chachamaru127/codex-harnessWrote 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/chachamaru127/codex-harness/handoff)<a href="https://agentmods.dev/skills/chachamaru127/codex-harness/handoff"><img src="https://agentmods.dev/badge/skills/chachamaru127/codex-harness/handoff/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/chachamaru127/codex-harness/handoff"><img src="https://agentmods.dev/badge/skills/chachamaru127/codex-harness/handoff.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.00076 | $0.01157 |
| Opus 5.5 | $0.00030 | $0.00463 |
| Sonnet 5.5 | $0.00015 | $0.00231 |
| Haiku 4.5 | $0.00008 | $0.00116 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Handoff Skill
PM-実装役間のハンドオフとワークフロー遷移を管理するスキル。
機能詳細
| 機能 | 詳細 |
|---|---|
| PM→実装役 | See references/handoff-to-impl.md |
| 実装役→PM | See references/handoff-to-pm.md |
| レビュー指摘自動修正 | See references/auto-fixing.md |
| コミット実行 | See references/execute-commit.md |
Quick Reference
- "Cursor に完了報告を書いて" →
/handoff cursor - "OpenCode にハンドオフ" →
/handoff opencode - "レビュー指摘を自動修正" →
/handoff auto-fix - "変更内容とテスト結果を含めて" → Includes git diff and test results
Prerequisites
This command should only run after harness-review APPROVE
| Condition | Required | Check Method |
|---|---|---|
| harness-review completed | Yes | Review result is APPROVE |
| No Critical/High issues | Yes | All fixed |
| Implementation complete | Yes | Plans.md tasks completed |
Why handoff requires review approval:
- PM receives unreviewed changes otherwise
- Quality not assured
- Breaks
/workflow (implement → review → fix → OK → handoff)
Usage
/handoff cursor # Handoff to Cursor
/handoff opencode # Handoff to OpenCode
Execution Flow
Step 1: Identify Completed Tasks
- Check Plans.md checkboxes
- Summarize work done
Step 2: Update Plans.md
# Before
- [ ] Task name `pm:依頼中`
# After
- [x] Task name `cc:完了` (YYYY-MM-DD)
Step 3: Gather Changes
git status -sb
git diff --stat
Step 4: Check CI/CD (if applicable)
gh run list --limit 3
Step 5: Generate Report
Output Format
## Completion Report
### Summary
- (1-3 lines describing what was done)
### Completed Tasks
- **Task Name**: [Task description]
### Changed Files
| File | Changes |
|------|---------|
| `path/to/file1` | [Summary] |
| `path/to/file2` | [Summary] |
### Verification Results
- [x] Build success
- [x] Tests passed
- [x] Manual verification complete
### Risks / Notes
- (If any)
### Next Actions (for PM)
1. [ ] [What PM should do next]
2. [ ] [Optional items]
What ships with it
5 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.
- 1mo ago First seen · 158 lines · 76 tokens per session scan A 5233f9466c6b
handoff is a skill published in the GitHub repository Chachamaru127/codex-harness (2 stars, last pushed 8mo ago), licensed MIT. It adds 76 tokens to every session and 1,157 once invoked, about $0.0003 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
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.