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 skills/reloru/new-relo/deploynpx skills add reloru/new-relo --skill deploygit clone --depth 1 https://github.com/reloru/new-reloWhat 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 | $0.00060 | $0.01059 |
| Opus 5 | $0.00030 | $0.00530 |
| Sonnet 5 | $0.00012 | $0.00212 |
| Haiku 4.5 | $0.00006 | $0.00106 |
Grade A, and why
deploy scanned grade A with 1 finding 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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
allowed-tools: Bash(node --check *), Bash(git status *), Bash(git branch *), Bash(npx wrangler deploy *), Bash(curl *) How it starts
The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deploy the Worker
Ship the Worker source under src/ to the crosbynews Worker and confirm the
live site is healthy. Auth comes from CLOUDFLARE_ZONE_API_TOKEN (preferred — see
CLAUDE.md's Deploy section) or CLOUDFLARE_API_TOKEN, paired with
CLOUDFLARE_ACCOUNT_ID either way (never a zone id — wrangler has no such
concept) — never run wrangler login (it clobbers the token auth).
If $ARGUMENTS contains --dry-run, run step 1, then the dry-run in step 3, and
stop — nothing is uploaded and nothing goes live.
1. Pre-flight — syntax gate
Mirror CI's gate before shipping. If this fails, STOP — do not deploy. It covers
every file under src/, not just the entry point: node --check validates one
file at a time and doesn't follow imports, so checking only src/index.js would
pass while an imported module was unparseable.
find src -name '*.js' -print0 | xargs -0 -n1 node --check
Then the cross-module reference check and the renderer sweep (both pure node, no install):
node scripts/check-module-refs.mjs
node scripts/check-renders.mjs
node scripts/test-health.mjs
node --check catches syntax errors but NOT a missing or renamed export — the
dry-run in step 3 catches that, so treat it as a merge gate, not an optional
extra. And NEITHER catches a module using another module's export without
importing it, because esbuild treats an unresolved identifier as a global. That
is what check-module-refs.mjs is for; run all three.
2. Pre-flight — know what you're shipping
npx wrangler deploy uploads the current working tree, not git. Deploying
from a feature branch pushes that code straight to production, bypassing the
PR + Syntax check gate. Check first:
git branch --show-current
git status --short
- Not on a clean
main? Say so and confirm the intent is a direct prod push from this working tree before continuing. - The canonical path is merge-to-
main→ CI deploys. A manual deploy is for out-of-band / urgent ships.
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.
- 2d ago First seen · 86 lines · 60 tokens per session scan A 40229d918c3e
deploy is a skill published in the GitHub repository reloru/new-relo (1 stars, last pushed 6d ago), licensed MIT. It adds 60 tokens to every session and 1,059 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
prepare-cloudflare-production-deployment
Source-of-truth runbook for preparing this Vinext Cloudflare Workers SaaS template for production deployment. Use when setting up or auditing Cloudflare MCP resources, wrangler.jsonc bindings, Worker secrets, Turnstile, Email Sending, GitHub Actions secrets/variables, or GitHub CLI deployment wiring for this…
review-configuration
Config, env, wrangler review. USE WHEN: user runs /review-configuration or explicitly asks for this review. DO NOT USE WHEN: implementing features or fixing bugs unless the user asked for a review.
review-wrangler
Wrangler/Workers config review (wrangler.jsonc files, compatibility dates, bindings, observability, generated types) against current official Cloudflare best practices. USE WHEN: user runs /review-wrangler or explicitly asks for this review. DO NOT USE WHEN: reviewing app code, other dev dependencies, or implementing…
cloudflare-maxxing
Educate on and recommend how to use the Cloudflare platform to its maximum. Use when the user asks what they can do with Cloudflare, how to use a Cloudflare feature, which Cloudflare product fits a need ("how do I do X on Cloudflare"), how to get more value from their account, or wants to learn the platform. Pairs…
source-command-cf-refresh
Capture a fresh Cloudflare snapshot, regenerate the report + beta advisor, and rebuild the dashboard data.
dns
DNS record management, Cloudflare API automation, TTL strategy, Let's Encrypt DNS challenges, split-horizon DNS, and resolver debugging for production domains.