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 jsgerman-oss/blackrim-nimbus-skills --skill cf-networking-and-edgegit clone --depth 1 https://github.com/jsgerman-oss/blackrim-nimbus-skillsWrote 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/jsgerman-oss/blackrim-nimbus-skills/cf-networking-and-edge)<a href="https://agentmods.dev/skills/jsgerman-oss/blackrim-nimbus-skills/cf-networking-and-edge"><img src="https://agentmods.dev/badge/skills/jsgerman-oss/blackrim-nimbus-skills/cf-networking-and-edge/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/jsgerman-oss/blackrim-nimbus-skills/cf-networking-and-edge"><img src="https://agentmods.dev/badge/skills/jsgerman-oss/blackrim-nimbus-skills/cf-networking-and-edge.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.00065 | $0.02678 |
| Opus 5 | $0.00032 | $0.01339 |
| Sonnet 5 | $0.00013 | $0.00536 |
| Haiku 4.5 | $0.00006 | $0.00268 |
Grade A, and why
cf-networking-and-edge 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 12d 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.
How it starts
The opening of the file, as written. The whole thing — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cloudflare Networking and Edge
When to use
- Setting up or migrating authoritative DNS to Cloudflare.
- Configuring CDN cache rules, transform rules, or purge strategies.
- Standing up load balancing with geo, latency, or weighted routing.
- Reducing origin latency with Argo Smart Routing.
- Exposing TCP/UDP services (beyond HTTP) via Spectrum.
- Securely connecting a private server or network to Cloudflare without opening inbound firewall rules (Cloudflare Tunnel).
- Connecting branch offices or cloud VPCs to Cloudflare's backbone (Magic WAN / Magic Transit).
DNS (authoritative)
Cloudflare is the authoritative DNS resolver for zones it manages. DNS changes propagate globally within seconds.
Defaults
- Proxy status (orange cloud): enable for any A/AAAA/CNAME record you want behind Cloudflare's CDN, WAF, and DDoS protection. Leave unproxied (grey cloud) only for records that must resolve to the origin IP directly (mail servers, SFTP, internal tooling).
- DNSSEC: enable for every zone. Cloudflare manages signing automatically after you add the DS record to the registrar. DNSSEC prevents on-path resolver cache poisoning.
- CAA records: add CAA records specifying your CA to prevent misissued certificates (
issue,issuewild,iodef). - TTL: for proxied records, Cloudflare overrides TTL to 300 s regardless of your setting — that is intentional. For unproxied records, set TTL to 300 s during migrations; raise to 3600 s+ once stable.
- API-managed DNS: use Terraform (
cloudflare_recordresource) or Wrangler for DNS records that are part of a Worker deployment. Do not mix console clicks and IaC for the same zone.
CDN — Cache Rules and Transform Rules
Cache rules
- Cloudflare's Cache Rules (zone-level) replace the older Page Rules — use Cache Rules for all new configurations. Page Rules are a legacy feature and will be deprecated.
- Set cache eligibility explicitly per path:
cache everythingfor static assets;bypass cachefor authenticated API endpoints. - Edge cache TTL: how long Cloudflare holds the response. Set via
Cache-Control: s-maxage=<seconds>from origin, or override with a Cache Rule. - Browser cache TTL: how long the client holds the response. Do not let Cloudflare's default override origin
Cache-Controlunless you have a specific reason. - Cache keys: vary on headers (
Accept-Encoding,Accept-Language) only if your origin actually serves different responses per header; unnecessary variation fragments the cache.
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.
- 12d ago First seen · 171 lines · 65 tokens per session scan A 268f9b3be92a
cf-networking-and-edge is a skill published in the GitHub repository jsgerman-oss/blackrim-nimbus-skills (8 stars, last pushed 26d ago), licensed MIT. It adds 65 tokens to every session and 2,678 once invoked, about $0.0003 per session on Opus 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-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-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 disaster recovery setup or full cluster backups (use gke-backup-dr instead).
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (auditcluster.sh), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny…
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".
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…