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 deploygit 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/deploy)<a href="https://agentmods.dev/skills/receptron/mulmoterminal/deploy"><img src="https://agentmods.dev/badge/skills/receptron/mulmoterminal/deploy/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/deploy"><img src="https://agentmods.dev/badge/skills/receptron/mulmoterminal/deploy.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.00027 | $0.00498 |
| Opus 5.5 | $0.00011 | $0.00199 |
| Sonnet 5.5 | $0.00005 | $0.00100 |
| Haiku 4.5 | $0.00003 | $0.00050 |
Grade A, and why
blueprint-cloudflare-deploy 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.
What it actually says
Publish to Cloudflare
This step's gates are deploy-production and credential: the user has approved publishing, and signing in to their Cloudflare account.
yarn wrangler whoami. If not signed in, ask the person, through the blueprint question tool, to runyarn wrangler loginin this folder themselves and tell you when it is done. Never handle an API token.- Create the database once:
yarn wrangler d1 create <name>and put thedatabase_idit prints intowrangler.jsonc. Apply the migrations to it:yarn wrangler d1 migrations apply DB --remote. Ifwrangler.jsoncbinds R2 buckets, create each once too (yarn wrangler r2 bucket create <bucket_name>): the deploy fails on a binding to a bucket that does not exist. - Secrets the app needs: ask the person to run
yarn wrangler secret put <NAME>themselves. yarn build, then give this build an id and ship it with the site:node -e 'console.log(require("crypto").randomUUID())' > .blueprint/build-id && cp .blueprint/build-id dist/client/blueprint-build.txt, thenyarn wrangler deploy.- Write the URL it published to (
https://…workers.dev, or the custom domain the spec names) to.blueprint/deploy-url, and tell the person the URL.
Done when the check passes: the URL in .blueprint/deploy-url serves the id this deploy wrote, answers
/api/health, sends a Content-Security-Policy, and its page renders text in headless Chrome.
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.
- Never enable billing, deploy to production, delete data or handle a credential unless this step's gates say the user approved exactly that.
- 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 First seen · 34 lines · 27 tokens per session scan A 7e596ed2564c
blueprint-cloudflare-deploy is a skill published in the GitHub repository receptron/mulmoterminal (245 stars, last pushed yesterday), licensed MIT. It adds 27 tokens to every session and 498 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-30.
Other skills, from other repositories
moai-platform-deployment
Deployment and hosting platform specialist covering Vercel, Railway, and Convex. Use when deploying applications, configuring edge functions, setting up continuous deployment, or managing serverless infrastructure.
moai-platform-database-cloud
Cloud database platform specialist covering Neon (serverless PostgreSQL), Supabase (PostgreSQL 16 with real-time), and Firebase Firestore (NoSQL with offline sync). Use when choosing or setting up cloud databases.
stack-baseline
The pinned default technology stack for SMB Product-Builder products. One source of truth so the architect, app-scaffolder, auth-engineer, and senior-dev never re-decide the stack per build — they build ON it. Covers framework, ORM/DB, auth, UI, payments/email/SMS, files, jobs, testing, hosting, and observability…
deploy-landed
A deployment verification procedure that checks whether the intended code revision is actually running, its environment settings are present, and the product works. A deployment is the process of putting new software on a server or hosting platform.
loom-kubernetes
Kubernetes deployment, cluster architecture, security, and operations. Not for: a loom orchestration job or CI pipeline job — see loom-ci-cd.
loom-prometheus
Prometheus monitoring and alerting for cloud-native observability. Not for: a loom orchestration job or CI pipeline job — see loom-ci-cd.