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 commands/jackofall1232/l00prite/handoff-summarygit clone --depth 1 https://github.com/jackofall1232/l00priteWrote 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/commands/jackofall1232/l00prite/handoff-summary)<a href="https://agentmods.dev/commands/jackofall1232/l00prite/handoff-summary"><img src="https://agentmods.dev/badge/commands/jackofall1232/l00prite/handoff-summary.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.00000 | $0.00304 |
| Opus 5 | $0.00000 | $0.00152 |
| Sonnet 5 | $0.00000 | $0.00061 |
| Haiku 4.5 | $0.00000 | $0.00030 |
Grade A, and why
handoff-summary 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 Summary Prompt
Path convention: every
.l00prite/path in this prompt is relative to the protocol root — the directory that contains the.l00prite/folder. In a project scaffolded by build-loop that is thel00prite/directory at the repo root (memory atl00prite/.l00prite/); in the l00prite source repo it is the repo root itself.
Prepare a cross-agent handoff for a l00prite-managed project.
Read .l00prite/blueprint.md, .l00prite/ledger.md, .l00prite/memory.md, .l00prite/constraints.md, .l00prite/failures.md, .l00prite/todos.md, .l00prite/state.json, and .l00prite/heartbeat.json.
Write or update HANDOFF.md with:
- Current mission and architecture summary
- Current status and active goal
- Recently completed work
- Known constraints and decisions
- Failed approaches / do-not-retry notes
- Verification status
- Blockers or human review gates
- Execution mode status (
heartbeat.jsonexecution.enabled,execution.current_iteration/execution.max_iterations, and the last run boundary, if the project has anexecutionblock) - Next smallest useful step
- Which
.l00prite/files were updated
Do not implement project features while producing a handoff.
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 · 26 lines · 0 tokens per session scan A 4320ba29dd42
handoff-summary is a command published in the GitHub repository jackofall1232/l00prite (9 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 304 tokens. 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 commands, from other repositories
annotate-plan
Draft a plan and open it in the annotator UI for user review.
docs
Command "docs" from tilework-tech/nori-skillsets, covering noridoc: commands, how it fits into the larger codebase, core implementation and things to know.
init
Scaffold a new plugin marketplace, or a standalone plugin.
bump
Version a local plugin from its commits and sync everything downstream.
build
Generate the Codex and Cursor registries from the catalog.
sync
Reconcile the catalog and the docs with the plugins on disk.