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 authgit 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/auth)<a href="https://agentmods.dev/skills/receptron/mulmoterminal/auth"><img src="https://agentmods.dev/badge/skills/receptron/mulmoterminal/auth/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/auth"><img src="https://agentmods.dev/badge/skills/receptron/mulmoterminal/auth.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.00023 | $0.00434 |
| Opus 5.5 | $0.00009 | $0.00174 |
| Sonnet 5.5 | $0.00005 | $0.00087 |
| Haiku 4.5 | $0.00002 | $0.00043 |
Grade A, and why
blueprint-cloudflare-auth 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 16d 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
Sign-in
A published Worker can be opened by anyone who has its URL. Read the spec's sign-in choice.
- None: only what the spec says a visitor may see and do is reachable. Say so on the main screen's footer.
test/auth.test.tsproves an operation the spec reserves (if any) is refused without a session. - One shared password: a sign-in screen; the password's PBKDF2 hash (Web Crypto, per-install salt) as a wrangler
secret (
.dev.varslocally, in.gitignore); a signed, HttpOnly, Secure, SameSite=Lax session cookie; every/apiroute except/api/healthand sign-in refuses without it. - One account per person: a
userstable (PBKDF2 hash with a per-user salt), sign-in and sign-out, roles if the spec lists them, checked on the server for every route. If the spec says only a company's people may sign in, Cloudflare Access in front of the Worker is the simplest door: say so in.blueprint/open-questions.md.
test/auth.test.ts: a request without a session is refused, with one it passes; a wrong password is refused.
Done when the check passes: yarn build and yarn test succeed and test/ has the auth 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.
- 16d ago Changed · +7 lines · +2 tokens per session a733ae50d109
- 18d ago First seen · 23 lines · 21 tokens per session scan A 880afd8abf59
blueprint-cloudflare-auth is a skill published in the GitHub repository receptron/mulmoterminal (238 stars, last pushed today), licensed MIT. It adds 23 tokens to every session and 434 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
verify
Verify that a change really works before you claim completion.
moai-ref-testing-pyramid
Test pyramid strategy, coverage targets, test patterns, and quality metrics reference. Agent-extending skill that amplifies manager-develop test-creation and quality-validation work with production-grade testing patterns. NOT for: production code implementation, architecture design, DevOps, security audits.
loom-c
C language expertise (C11/C17/C23) for memory-safe, portable, production-quality systems code.
loom-test-strategy
Test strategy guidance covering pyramid design, coverage, test categorization, flaky tests, infrastructure, and risk-based prioritization.
loom-testing
Test implementation across unit, integration, e2e, security, infrastructure, data pipeline, and ML domains.
test-generator
Automatically suggest tests for new functions and components. Use when new code is written, functions added, or user mentions testing. Creates test scaffolding with Jest, Vitest, Pytest patterns. Triggers on new functions, components, test requests, testing mentions.