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 skills/chachamaru127/codex-harness/handoffnpx skills add Chachamaru127/codex-harness --skill handoffgit 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.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.00076 | $0.01157 |
| Opus 5 | $0.00038 | $0.00579 |
| Sonnet 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 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.
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.
- 4d 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 6mo ago), licensed MIT. It adds 76 tokens to every session and 1,157 once invoked, about $0.0004 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
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…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
flow-next-tracker-sync
Project a flow-next spec to a tracker issue (Linear, GitHub, GitLab, Jira) and reconcile two-way. Use when asked to sync to a tracker. NOT plan-sync.
loop
Full execution protocol for MODE: LOOP — the compound-engineering loop: brainstorm → plan → build → review → improve, iterating under defense-in-depth stop conditions with generator/critic separation, durable resumable state, and mandatory compounding learning capture. Loaded on demand by the architect when the loop…
subagent-delegation
Canonical protocol for delegating GSD work to native Antigravity subagents — when to delegate, how to invoke, workspace isolation modes, and the inline fallback for older IDE versions.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.