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 apigit 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/api)<a href="https://agentmods.dev/skills/receptron/mulmoterminal/api"><img src="https://agentmods.dev/badge/skills/receptron/mulmoterminal/api/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/api"><img src="https://agentmods.dev/badge/skills/receptron/mulmoterminal/api.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.00022 | $0.00378 |
| Opus 5.5 | $0.00009 | $0.00151 |
| Sonnet 5.5 | $0.00004 | $0.00076 |
| Haiku 4.5 | $0.00002 | $0.00038 |
Grade A, and why
blueprint-cloudflare-api 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
API
- One route per operation in the spec's API table, in the Worker's
/api/*handler. - At the entry, before routing and before sign-in:
- a POST / PUT / PATCH / DELETE whose
Origin(or, without one,Referer) is not this Worker's own origin is refused with 403; - a JSON body is read once, and a malformed one is refused with 400 for every path. A Worker reads bodies per route by default, which leaves a malformed body to whatever the route does with it.
- a POST / PUT / PATCH / DELETE whose
- Validate every body and parameter (zod is fine) and answer 400 with a message when it is wrong; 404 for a missing row. Every error reaches one handler that answers JSON without a stack trace.
test/api.test.ts: every route in both directions — the valid request succeeds with the right body, an invalid one is refused with 400 — throughSELF.fetch.
Done when the check passes: yarn build and yarn test succeed and test/ has the api tests.
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 · +5 lines a50a8df9d6fd
- 27d ago First seen · 23 lines · 22 tokens per session scan A 52062f4298b9
blueprint-cloudflare-api is a skill published in the GitHub repository receptron/mulmoterminal (245 stars, last pushed yesterday), licensed MIT. It adds 22 tokens to every session and 378 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
Spring Test Pyramid
Unit, integration, slice, and E2E test patterns for Spring Boot applications.
sync-new-data-type
Adds scaffolding for a new Sync data type in Chromium across protocol buffers, DataType definitions, feature flags, controller builders, unit tests, and metrics.
verify
Verify that a change really works before you claim completion.
generate-testability-wrappers
DO NOT USE when the target already consumes an injected interface or built-in abstraction such as IFileSystem or TimeProvider, even if the request says "generate a wrapper"; no new wrapper is needed. Use only when C# source calls an ambient/static dependency and no injectable seam exists: first-time TimeProvider…
convex-test
Generate convex-test tests for the app's Convex functions.
testing
Testing and code quality context for Jest, React Testing Library, ESLint, and test patterns. Use when writing tests or fixing linting issues.