What is cf-validator?

A background helper that updates project tracking files after implementation work. It records plans, progress, completed steps, blockers, and findings in files such as plan.md and progress.md.

Use it to check off plan items, update the current phase or step, log completed actions, and record errors or blockers in the active project directory.

It keeps project records current without requiring the developer to stop and maintain them manually.

cf-validator — Agent for Claude Code by superbenefit/sb-marketplace

Install

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.

Clone the repo

git clone --depth 1 https://github.com/superbenefit/sb-marketplace

Made for: Claude Code.

Or install cloudflare-dev, the plugin that ships this one along with the rest of its 1 skill, 4 commands, 3 agents.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/superbenefit/sb-marketplace/cf-validator/github.svg)](https://agentmods.dev/agents/superbenefit/sb-marketplace/cf-validator)

Your own site

<a href="https://agentmods.dev/agents/superbenefit/sb-marketplace/cf-validator"><img src="https://agentmods.dev/badge/agents/superbenefit/sb-marketplace/cf-validator/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/superbenefit/sb-marketplace/cf-validator"><img src="https://agentmods.dev/badge/agents/superbenefit/sb-marketplace/cf-validator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 553 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00016	$0.00553
Opus 5.5	$0.00006	$0.00221
Sonnet 5.5	$0.00003	$0.00111
Haiku 4.5	$0.00002	$0.00055

Measured 1mo ago against content hash 4eb929d4eff0, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

cf-validator 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 1mo 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.

cloudflare-dev/agents/cf-validator.md · 59 lines

How it starts

The opening of the file, as written. The whole thing — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a Cloudflare best practices validator. Your job is to:

Read the project's configuration and implementation files
Compare against current Cloudflare platform best practices
Report discrepancies with file:line references
Suggest corrections with code examples

Validation Checklist

Configuration (wrangler.jsonc)

compatibility_date is set (>= "2025-03-07" for Agents)
compatibility_flags includes "nodejs_compat"
observability: { enabled: true } is present
migrations block includes new_sqlite_classes for all Agent/DO classes
All bindings are correctly declared (KV, R2, D1, Vectorize, DO, Queues, AI)

Package Dependencies (package.json)

agents package is installed (for Agents SDK)
@modelcontextprotocol/sdk is installed (for MCP servers)
workers-oauth-provider is installed (if using OAuth)
No deprecated or conflicting packages

MCP Server Patterns

Uses createMcpHandler for stateless MCP servers (recommended)
If using McpAgent: server declared as class property, tools in init()
Tool parameters use Zod schemas with descriptions
Error responses use isError: true

Agent Patterns

Agent class extends Agent<Env, State> with proper type parameters
State is JSON-serializable
WebSocket uses hibernation API (not legacy addEventListener)
SQL uses tagged template literals (this.sql\...``)

API Patterns

Reranker uses batch API (query + contexts, not text: [...])
Vectorize queries respect topK limits per returnMetadata setting
R2 accessed via bindings (not REST API from Workers)
D1 uses prepared statements (not string concatenation)

Workflow Patterns

All steps are awaited
Steps are idempotent
No side effects outside steps
Bindings accessed via this.env (not closures)

Output Format

Return a structured report:

✅ Compliant items
❌ Non-compliant items with file:line references and fixes
⚠️ Warnings and recommendations

Read the full file on GitHub · 59 lines

Changes

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.

1mo ago First seen · 59 lines · 16 tokens per session scan A 4eb929d4eff0

Subscribe to this mod's changes

cf-validator is an agent published in the GitHub repository superbenefit/sb-marketplace (5 stars, last pushed 8mo ago), licensed CC0-1.0. It adds 16 tokens to every session and 553 once invoked, about $0.0001 per session on Opus 5.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.

Cloud DevOps and cloud

cloud-agent

Own the cloud lane — AWS/Azure/GCP posture + active exploitation, IaC scanning, container/K8s escape, and SSRF→metadata credential pivots. Returns cloud findings with the misconfig→impact chain, not raw scanner dumps.

TyrusRC/praetor · 53 tokens

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.

ivegamsft/basecoat · 37 tokens

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.

armanzeroeight/fastagent-plugins · 35 tokens

deployment-verifier

Verifies local deployment health — checks ports, starts app, polls health endpoint, inspects Docker containers.

asysta-act/agent-flow · 24 tokens

tunnel-doctor

Diagnoses tunnel client/relay problems. Use when a tunnel fails to connect, requests through the public URL hit connection refused or 502, the daemon doesn't reach connected, name conflicts occur, or the user wants the setup audited before exposing a port. Runs tunnel doctor, inspects daemon state, and checks relay…

anivaryam/anivaryam-plugins · 77 tokens

grumpy-budget-hawk

Cloud cost reviewer. Analyses infrastructure and code changes for cost impact, over-provisioning, and unbounded resource consumption.

JackScammell/Parliament-Of-Chaos · 31 tokens