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 skills add receptron/mulmoterminal --skill handovergit clone --depth 1 https://github.com/receptron/mulmoterminalWrote 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/receptron/mulmoterminal/handover)<a href="https://agentmods.dev/skills/receptron/mulmoterminal/handover"><img src="https://agentmods.dev/badge/skills/receptron/mulmoterminal/handover/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/skills/receptron/mulmoterminal/handover"><img src="https://agentmods.dev/badge/skills/receptron/mulmoterminal/handover.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.00036 | $0.00572 |
| Opus 5.5 | $0.00014 | $0.00229 |
| Sonnet 5.5 | $0.00007 | $0.00114 |
| Haiku 4.5 | $0.00004 | $0.00057 |
Grade A, and why
blueprint-cloudflare-handover 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 25d 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 — 37 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Handover
Write README.md in the spec's language, for someone who is not an engineer:
- What the app does, in two sentences, and where it is published (the URL in
.blueprint/deploy-url). - Running it on this computer:
yarn installonce, thenyarn buildandyarn start, then the address to open. - Publishing a change: try it with
yarn startfirst, thenyarn deploy(it runswrangler deploy); a schema change is a new migration, applied withyarn wrangler d1 migrations apply DB --remotebefore the deploy. - The data: it is in D1 on Cloudflare. Back it up with
yarn wrangler d1 export DB --remote --output backup.sql, and how to restore it. - Who can open it (anyone with the URL, or only signed-in people) and how to change that.
Then write .blueprint/start-here.md, in the spec's language — what the person sees the moment the build finishes:
- Open it — the published URL, and who can sign in and how.
- Check that it works — one checkbox per must-have in the spec, each an action and what should happen
(
- [ ] 本を 1 冊登録する → 一覧に出る), with the app's real screen and button names; one for someone who should be refused being refused. - The next change — try it with
yarn start, thenyarn deploy. - Your data — the one-line backup, and where the security review is (
.blueprint/security-review.md).
Done when the check passes: the README explains yarn start, yarn deploy and wrangler d1 export, and
.blueprint/start-here.md names the published URL and has the checklist.
Always
- Read
.blueprint/spec.mdfirst. It is the agreed specification; do not widen it. - When you need a decision, ask it through the blueprint question tool and stop. Do not guess.
- Do not run
git init: a new repository loses the folder's trust and the next unattended step stops at Claude Code's trust prompt. The user adds git themselves after the build if they want it. - Say you are done by stopping; the executor runs the check. Do not claim success yourself.
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.
- 25d ago Changed · +13 lines · +5 tokens per session ff404fbb901c
- 27d ago First seen · 24 lines · 31 tokens per session scan A 61890a12ac1a
blueprint-cloudflare-handover is a skill published in the GitHub repository receptron/mulmoterminal (245 stars, last pushed yesterday), licensed MIT. It adds 36 tokens to every session and 572 once invoked, about $0.0001 per session on Opus 5.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-28.
Other skills, from other repositories
moai-ref-ui-polish
UI polish and interface-completion reference: the small visual details — concentric border radius, optical alignment, shadow-vs-border, motion easing, typography smoothing, tabular numbers, icon stroke weight, hit areas — that separate polished interfaces from generic ones. Agent-extending skill that amplifies…
self-assessment
Interactive skill assessment with personalized learning path generation.
project-design
Roteador de processos de design e marca que carrega orientações para criar arquivos DESIGN.md completos para um projeto e suas aplicações de interface.
loom-swift
Swift language expertise for idiomatic, production-quality code.
loom-usage
Meta-orchestration skill for Claude driving loom itself.
loom-c
C language expertise (C11/C17/C23) for memory-safe, portable, production-quality systems code.