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-zero-trust-and-securitygit 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-zero-trust-and-security)<a href="https://agentmods.dev/skills/jsgerman-oss/blackrim-nimbus-skills/cf-zero-trust-and-security"><img src="https://agentmods.dev/badge/skills/jsgerman-oss/blackrim-nimbus-skills/cf-zero-trust-and-security/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-zero-trust-and-security"><img src="https://agentmods.dev/badge/skills/jsgerman-oss/blackrim-nimbus-skills/cf-zero-trust-and-security.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.00077 | $0.02935 |
| Opus 5 | $0.00039 | $0.01468 |
| Sonnet 5 | $0.00015 | $0.00587 |
| Haiku 4.5 | $0.00008 | $0.00294 |
Grade A, and why
cf-zero-trust-and-security 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cloudflare Zero Trust and Security
When to use
- Putting identity-aware access control in front of an internal application or SSH/RDP target.
- Filtering DNS and HTTP egress from managed devices via Gateway.
- Reviewing or writing WAF custom rules; enabling managed rulesets.
- Enabling Bot Management for a public site that experiences credential stuffing, scraping, or fraud.
- Auditing DDoS posture or enabling Magic Firewall for network-layer filtering.
- Enabling Page Shield to detect malicious scripts loaded by your frontend.
- Securing an API surface with API Shield (schema validation, mutual TLS, sequence mitigation).
Cloudflare Access (ZTNA)
Access is an identity-aware reverse proxy. It terminates TLS, verifies the caller's identity (via an identity provider), evaluates policy, then forwards to the origin or Tunnel.
Defaults
- Applications: create one Access Application per protected resource. Types: Self-hosted (HTTP/HTTPS via Tunnel or public hostname), SSH, RDP, Infrastructure (SSH/RDP with browser rendering), SaaS (SAML/OIDC for SaaS apps).
- Identity providers: connect at least one corporate IdP (Okta, Entra ID, Google Workspace, JumpCloud). Use SAML or OIDC. Cloudflare's built-in one-time PIN (email OTP) is a fallback only — do not use it as the primary IdP for sensitive applications.
- Policies: Access policies are evaluated top-down with Allow / Block / Bypass actions. Default-deny: unless a rule explicitly allows, access is denied.
Include: who can attempt access.Require: additional conditions that must all pass (e.g.,Device Posture: disk encryption = on).Exclude: always deny regardless of includes.
- Device posture checks: require corporate device certificates, disk encryption, OS version minimum, or endpoint detection and response (EDR) agent enrollment. Combine with
Requirein the policy. - Service tokens: machine-to-machine access uses Access Service Tokens (client ID + secret) — never a user's identity token. Rotate service tokens on a schedule.
- Short-lived certificates: for SSH targets, issue short-lived certs (Access for Infrastructure) instead of distributing long-lived SSH keys.
- Audience tags: every Access Application has an AUD tag; validate it in Workers or origin apps to prevent access token replay from other applications.
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 · 175 lines · 77 tokens per session scan A 9cb9d2b78dad
cf-zero-trust-and-security is a skill published in the GitHub repository jsgerman-oss/blackrim-nimbus-skills (8 stars, last pushed 26d ago), licensed MIT. It adds 77 tokens to every session and 2,935 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
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…