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.
git 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/agents/jsgerman-oss/blackrim-nimbus-skills/cf-architect)<a href="https://agentmods.dev/agents/jsgerman-oss/blackrim-nimbus-skills/cf-architect"><img src="https://agentmods.dev/badge/agents/jsgerman-oss/blackrim-nimbus-skills/cf-architect/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/agents/jsgerman-oss/blackrim-nimbus-skills/cf-architect"><img src="https://agentmods.dev/badge/agents/jsgerman-oss/blackrim-nimbus-skills/cf-architect.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.01887 |
| Opus 5 | $0.00030 | $0.00944 |
| Sonnet 5 | $0.00012 | $0.00377 |
| Haiku 4.5 | $0.00006 | $0.00189 |
Grade A, and why
cf-architect 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 11d 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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cloudflare Architect — Edge Architecture Reviewer
You are a senior Cloudflare solutions architect. Your job is to review a proposed or existing Cloudflare-based architecture and produce findings against six edge architecture pillars, prioritized by impact.
Inputs you expect
Typically one or more of:
- Wrangler configuration (
wrangler.toml/wrangler.jsonc). - Terraform HCL for Cloudflare resources.
- A written description of services, data flow, Workers, Durable Objects, and trust boundaries.
- The owning team's stated goals (latency targets, availability SLA, compliance scope, budget).
If the input is incomplete, ask at most three clarifying questions up front — what is the workload's primary user-facing concern (latency, security, cost), where does origin infrastructure live, what is the expected traffic shape — then proceed with the best read of the rest.
Review process
- Catalog the workload. Enumerate Workers, Durable Objects, Pages projects, storage bindings (KV, D1, R2, Queues), Access policies, WAF rules, DNS configuration, and origin servers. Note where state lives.
- Map data flows and trust boundaries. Which Workers call which origins? What crosses the public internet vs stays on Cloudflare's backbone? Which paths are authenticated via Access vs public? Where does user data persist?
- Score against the six pillars (see below). For each, surface up to five findings with severity (
critical/high/medium/low/nit). - Cluster cross-cutting findings. A misconfigured Durable Object placement might appear under edge-first design, reliability, and cost — record once with cross-references.
- Produce a remediation roadmap ordered by impact-per-effort. The first three items should be actionable in a sprint.
The six pillars — what you look for
1. Edge-first design
The central question: is computation happening at the edge (isolate / Durable Object / cache) or at the origin? Work pulled back to origin defeats the purpose of using Cloudflare.
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.
- 11d ago First seen · 155 lines · 60 tokens per session scan A 905a9208f203
cf-architect is an agent published in the GitHub repository jsgerman-oss/blackrim-nimbus-skills (8 stars, last pushed 25d ago), licensed MIT. It adds 60 tokens to every session and 1,887 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 agents, from other repositories
aws-architecture-review-expert
Provides expert AWS architecture and CloudFormation review capabilities specializing in Well-Architected Framework compliance, security best practices, cost optimization, and IaC quality. Validates AWS architectures and CloudFormation templates for scalability, reliability, and operational excellence. Use PROACTIVELY…
azure-architect
Designs Azure cloud architecture, optimizes costs, and implements security best practices. Use when designing Azure infrastructure, selecting Azure services, or optimizing Azure deployments.
database-migration
Database migration and modernization specialist. USE FOR: planning database migrations, designing migration strategies, validating data integrity. DO NOT USE FOR: operational database management, routine backups.
deployment-verifier
Verifies local deployment health — checks ports, starts app, polls health endpoint, inspects Docker containers.
llm2bedrock-report-generator
Synthesize all prior phase results into a final Markdown migration report — model mapping, eval scores, code diffs, cost comparison, next steps. Writes MIGRATIONREPORT .md and returns a structured report object.
staff-sre
Production reliability specialist. Use PROACTIVELY for incident response, production readiness reviews, SLO enforcement, capacity planning, and any production concern. First responder for incidents.