Borrowing it
Nothing to install: this file belongs to reloru/new-relo. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/reloru/new-relo/main/.claude/skills/deploy/SKILL.mdgit clone --depth 1 https://github.com/reloru/new-reloWrote 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/reloru/new-relo/deploy)<a href="https://agentmods.dev/skills/reloru/new-relo/deploy"><img src="https://agentmods.dev/badge/skills/reloru/new-relo/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/reloru/new-relo/deploy"><img src="https://agentmods.dev/badge/skills/reloru/new-relo/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.00060 | $0.01059 |
| Opus 5.5 | $0.00024 | $0.00424 |
| Sonnet 5.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 2mo 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.
- 2mo 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 7d ago), licensed MIT. It adds 60 tokens to every session and 1,059 once invoked, about $0.0002 per session on Opus 5.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
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running security audits (auditcluster.sh), enforcing Network Policies (default-deny and Dataplane V2 logging), isolating high-risk pods inside GKE Sandbox (gVisor), enforcing Pod…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for generating K8s YAML manifests (use gke-manifest-generation) or disaster recovery…
cloud-architect
Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost…
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".