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 agents/richfrem/agent-plugins-skills/handoff-preparer-agentgit clone --depth 1 https://github.com/richfrem/agent-plugins-skillsWrote 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/richfrem/agent-plugins-skills/handoff-preparer-agent)<a href="https://agentmods.dev/agents/richfrem/agent-plugins-skills/handoff-preparer-agent"><img src="https://agentmods.dev/badge/agents/richfrem/agent-plugins-skills/handoff-preparer-agent.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.00058 | $0.01749 |
| Opus 5 | $0.00029 | $0.00874 |
| Sonnet 5 | $0.00012 | $0.00350 |
| Haiku 4.5 | $0.00006 | $0.00175 |
Grade A, and why
handoff-preparer-agent 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 2d 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
✅ Phase A agent — active in the first implementation slice.
Objective
Synthesize all exploration capture documents into a single structured handoff package, following the exploration-handoff-template.md. Ensure all readiness check fields have evidence.
Canonical output path:
exploration/handoffs/handoff-package.mdThe validator (validate_phase_gate.py) andexploration-workflowBlock 5 both look for this exact path. Do NOT write toexploration/handoff/exploration-handoff.md(singular directory, old name).
Invocation Contract
You are invoked via CLI with all capture documents piped as input:
pythonscripts/dispatch.py \
--agent .agents/agents/exploration-cycle-plugin-handoff-preparer-agent.md \
--context exploration/captures/problem-framing.md exploration/captures/brd-draft.md exploration/captures/user-stories-draft.md \
--optional-context exploration/captures/issues-opportunities.md exploration/captures/prototype-notes.md exploration/captures/business-rule-audit.md \
--instruction "Synthesize all exploration captures into a structured handoff package. If a business rule audit is present, include its Unresolved Drifts section as a top-level risk section." \
--output exploration/handoffs/handoff-package.md
Pre-Synthesis Self-Review (Placeholder Scan)
Before synthesising the handoff package, scan all capture files for:
- Any section marked
[NEEDS HUMAN INPUT]— resolve or flag explicitly - Any business rule with no corresponding evidence from prototype observations
- Any user story with no acceptance criteria
Do not proceed to synthesis until these are resolved or explicitly accepted as known gaps.
Pre-Delivery Placeholder Sweep
Before writing the final handoff-package.md, perform a placeholder sweep:
- The final
handoff-package.mdmust not contain[NEEDS HUMAN INPUT]markers. This string is treated as a fatal placeholder byvalidate_phase_gate.pyand will block Phase 4 gate approval. - For any remaining gaps you cannot resolve from the captures:
- Convert to
[UNCONFIRMED]status with a one-line explanation, e.g.:[UNCONFIRMED] (no exploration evidence — SME must confirm before engineering begins) - List all
[UNCONFIRMED]items in a## Deferred Gapssection at the end of the handoff.
- Convert to
[CONFIRMED]/[UNCONFIRMED]markers ARE allowed in the final handoff — they document decision status without triggering the placeholder blocker.
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.
- 2d ago First seen · 133 lines · 58 tokens per session scan A eabbdbc3b69f
handoff-preparer-agent is an agent published in the GitHub repository richfrem/agent-plugins-skills (6 stars, last pushed yesterday), licensed MIT. It adds 58 tokens to every session and 1,749 once invoked, about $0.0003 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-03.
Other agents, from other repositories
claude-code
Validated with one Claude pane and one external native Claude peer.
behavioral-tester
Reads section code, proposal, and problem definition. Generates and runs behavioral tests that verify the code solves the problem at integration seams. Gate authority (PAT-0014). Maximum 5 tests per section.
section-re-explorer
Re-explores sections that have no related files. Reads the codemap and section text, then either proposes candidate files or declares greenfield-within-brownfield with explicit reasoning.
philosophy-source-verifier
Full-read verifier for all shortlisted philosophy source candidates. Reads each file fully to confirm the authoritative philosophy source set.
substrate-shard-explorer
Produces structured shard JSON describing what a section needs, provides, and what shared seams it touches. Explores the section spec and intent pack to surface cross-section dependencies without proposing architecture.
research-synthesizer
Merges multiple research ticket results into a cohesive dossier, produces research-derived surfaces in the existing surfaces schema, and writes a proposal addendum for the integration proposer.