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-iac-and-deploymentgit 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-iac-and-deployment)<a href="https://agentmods.dev/skills/jsgerman-oss/blackrim-nimbus-skills/cf-iac-and-deployment"><img src="https://agentmods.dev/badge/skills/jsgerman-oss/blackrim-nimbus-skills/cf-iac-and-deployment/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-iac-and-deployment"><img src="https://agentmods.dev/badge/skills/jsgerman-oss/blackrim-nimbus-skills/cf-iac-and-deployment.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.00085 | $0.03410 |
| Opus 5 | $0.00043 | $0.01705 |
| Sonnet 5 | $0.00017 | $0.00682 |
| Haiku 4.5 | $0.00009 | $0.00341 |
Grade A, and why
cf-iac-and-deployment 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 — 320 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cloudflare IaC and Deployment
When to use
- Setting up a new Worker, Pages, or D1 project with production-grade defaults.
- Writing or reviewing
wrangler.toml/wrangler.jsoncfor multi-environment deploys. - Authoring or migrating Terraform for Cloudflare resources (especially v4 → v5 provider migration).
- Designing a CI/CD pipeline with GitHub Actions that deploys to Cloudflare using scoped API tokens.
- Managing Workers secrets safely across environments.
- Reviewing an existing IaC repo for drift, secret hygiene, or missing resources.
Wrangler (the Cloudflare CLI)
Wrangler is the canonical tool for developing, testing, and deploying Workers and Pages projects. Wrangler ≥ 4.x (npm install -D wrangler@latest) is required for current features.
wrangler.toml vs wrangler.jsonc
- Use
wrangler.toml(TOML format) unless your project has an existingwrangler.jsonc(JSON5 with comments) convention. wrangler.jsoncsupports comments and is friendlier for complex configs with inline documentation.- Do not mix formats in the same project.
Configuration structure
name = "my-worker"
main = "src/index.ts"
compatibility_date = "2025-01-01" # Pin; advance deliberately.
compatibility_flags = []
# Shared bindings (available in all environments)
[[kv_namespaces]]
binding = "SESSIONS"
id = "abc123..."
[env.production]
name = "my-worker-production"
[[env.production.kv_namespaces]]
binding = "SESSIONS"
id = "xyz789..." # Different namespace ID per environment.
[[env.production.d1_databases]]
binding = "DB"
database_name = "my-db-prod"
database_id = "..."
[env.production.placement]
mode = "smart" # Smart Placement for production if origin-latency matters.
Key rules:
compatibility_date: pin to a specific date; check Cloudflare's compatibility changelog before advancing.- Separate resource IDs per environment — never share a KV namespace or D1 database between production and development.
main: always explicit; never rely on convention defaults in production configs.- Secrets are NOT declared in
wrangler.toml— they are pushed viawrangler secret put.
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 · 320 lines · 85 tokens per session scan A fa1f1e3a94ea
cf-iac-and-deployment is a skill published in the GitHub repository jsgerman-oss/blackrim-nimbus-skills (8 stars, last pushed 26d ago), licensed MIT. It adds 85 tokens to every session and 3,410 once invoked, about $0.0004 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
atmos-hooks
Atmos hooks: lifecycle events, hook kinds, command/store/git/security hooks, step/steps hooks, when: conditions, scoping and overrides, toolchain integration, --skip-hooks, and Atmos Pro/local output.
atmos-modernization
Atmos Modernization: migrate deprecated or legacy Atmos patterns to current names, Native CI, Atmos Pro drift detection, dependencies.components, nametemplate, and declared secrets.
atmos-pro
Atmos Pro setup and workflows: settings.pro, GitHub OIDC, affected and inventory uploads, stack locks, pro commit, workflow dispatch, merge queues, and drift detection.
atmos-sbom
Atmos SBOM provenance: CycloneDX and SPDX generation from vendor and Terraform evidence, coverage diagnostics, NTIA validation, and native CI workflow-artifact publication.
atmos-version
Atmos Version Tracker: version tracks, lock files, managed external dependency versions, atmos version track commands, !version, file managers, update policy, pinning, and CI verification.
atmos-cache
Atmos caching: CI cache configuration and commands, GitHub Actions cache integration, Terraform registry cache mirror/list/prune/stats/trust, and cache modernization guidance.