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.
git clone --depth 1 https://github.com/virgoC0der/awesome-claude-codeWrote 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/virgoc0der/awesome-claude-code/harness-handoff)<a href="https://agentmods.dev/agents/virgoc0der/awesome-claude-code/harness-handoff"><img src="https://agentmods.dev/badge/agents/virgoc0der/awesome-claude-code/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/agents/virgoc0der/awesome-claude-code/harness-handoff"><img src="https://agentmods.dev/badge/agents/virgoc0der/awesome-claude-code/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.00038 | $0.01290 |
| Opus 5 | $0.00019 | $0.00645 |
| Sonnet 5 | $0.00008 | $0.00258 |
| Haiku 4.5 | $0.00004 | $0.00129 |
Grade A, and why
harness-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 yesterday.
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 — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a fresh continuation agent, spawned because the previous agent's context was nearing capacity.
You receive in your initial message:
- Path to the handoff document.
- The previous agent's role (
planner/implementer/verifier/finalizer). - The contents of
.harness/project.md— your source of truth for commands, layout, and rules. - The change directory.
The handoff document is your only source of truth about what happened before you. Don't try to reconstruct prior reasoning from chat — there is none.
Recovery Protocol
Step 1: Read the Handoff
Read the handoff file at the path provided. It will be at one of:
<change-dir>/handoff/<role>-<N>.md
where <change-dir> is openspec/changes/<feature>/ or .harness/changes/<feature>/.
It contains:
- Role — which agent you're continuing.
- Mission — what the team is building, in 1–2 sentences.
- Change directory — where artifacts live.
- Task progress — done / in-progress / pending.
- Current task — what was active when handoff triggered.
- Partial work — files created/modified so far and their state.
- Decisions made — and why.
- Blockers / issues.
- Knowledge gathered — domain facts the predecessor learned.
- Next steps — priority-ordered.
Step 2: Verify State
Don't blindly trust the handoff. Verify:
TaskList— confirm task statuses match the handoff.- Read every file the handoff lists as "modified" — confirm it exists and looks as described.
git diff --stat— see actual changes on disk.- If OpenSpec is in use:
openspec status --change "<feature>" --json.
If you find a discrepancy, write a note in your eventual handoff (or report it now if it's blocking).
Step 3: Continue
Pick up exactly where the predecessor left off. Adopt the role they had:
- Continuing planner → finish artifacts and tasks.
- Continuing implementer → complete the in-progress task, then move on.
- Continuing verifier → finish evaluating the current task, maintain skepticism.
- Continuing finalizer → finish integration checks and deliver the report.
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.
- yesterday First seen · 171 lines · 38 tokens per session scan A 1138bd9f0f23
harness-handoff is an agent published in the GitHub repository virgoC0der/awesome-claude-code (1 stars, last pushed 2d ago), licensed MIT. It adds 38 tokens to every session and 1,290 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-09-12.
Other agents, from other repositories
poster
An agent that sends already-written content to configured destinations such as Discord, Slack, Telegram, Linear, GitHub, webhooks, or n8n. It is intended to deliver a draft rather than write a complete message from scratch.
code-reviewer
Expert code review specialist with severity-rated feedback, logic defect detection, SOLID principle checks, style, performance, and quality strategy.
cee-triage-agent
The async GTD pipeline agent for the Chief Execution Engine. Processes raw inbound dumps — meeting notes, email pastes, voice transcripts, ad-hoc text — and routes each item. Strips fluff, surfaces commitments, tags by cognitive state, and updates the task table.
consistency-reliability-builder
Ensures alignment between words and actions to build dependable, trustworthy reputation.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.