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 rules/xiaomaimuchanyiyiba/agent-handoff/handoffgit clone --depth 1 https://github.com/xiaomaimuchanyiyiba/agent-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/rules/xiaomaimuchanyiyiba/agent-handoff/handoff)<a href="https://agentmods.dev/rules/xiaomaimuchanyiyiba/agent-handoff/handoff"><img src="https://agentmods.dev/badge/rules/xiaomaimuchanyiyiba/agent-handoff/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.00038 | $0.00536 |
| Opus 5 | $0.00019 | $0.00268 |
| Sonnet 5 | $0.00008 | $0.00107 |
| Haiku 4.5 | $0.00004 | $0.00054 |
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 6d 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.
What it actually says
Handoff — Project Handover
Write handoff docs under .handoff/ directory, with HANDOFF.md as a symlink to the latest. The next person should need zero follow-up questions.
Artifact Layout
.handoff/
├── 2026-05-11.md # timestamped entries (YYYY-MM-DD)
├── 2026-05-11.001.md # subsequent entries same day
└── 2026-05-10.md
HANDOFF.md -> .handoff/2026-05-11.md # symlink to latest
.handoff/is gitignoredHANDOFF.mdsymlink is updated on every write
Mode Detection
- No
.handoff/files + noHANDOFF.md→ Wave mode: write a new handoff .handoff/exists orHANDOFF.mdexists + user says "take over" → Land mode- Exists + unclear intent → Ask
Backward compat: standalone HANDOFF.md (not symlink) is detected as legacy — migrate on first Wave.
Wave Mode — Write Handoff Doc
- Create
.handoff/if missing - Generate filename:
YYYY-MM-DD.md(first today) orYYYY-MM-DD.001.mdetc. - Write content to
.handoff/<filename> ln -sf .handoff/<filename> HANDOFF.md- Add
.handoff/to.gitignoreif missing
Core sections: Project Overview, Startup, Directory Structure, Current Status, Next Steps. Supplementary sections: as needed (DB, API, routes, agents, etc.).
Match the user's language. Mark unknowns as ⚠️ TBD.
Land Mode — Take Over
- Find latest:
.handoff/files sorted by name desc, or followHANDOFF.mdsymlink - Read all referenced docs
- Report findings first, wait for confirmation
- Execute TODOs by priority, create new timestamped handoff after each change
Universal Principles
- No guessing, no sugarcoating
- Analyze before acting
- Keep the trail — new file per update, never overwrite history
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.
- 6d ago First seen · 57 lines · 38 tokens per session scan A af3d540a96ec
handoff is a cursor rule published in the GitHub repository xiaomaimuchanyiyiba/agent-handoff (2 stars, last pushed 3mo ago), licensed MIT. It adds 38 tokens to every session and 536 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 cursor rules, from other repositories
frontend
Demo Shop frontend guidance.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.