Skip to main content

Platform SDK Plugin

AI enforcement for Cloudflare Workers cost safety.

Claude Code plugin with rules, skills, agents, and hooks that enforce Platform SDK best practices and catch Cloudflare Workers cost risks during development.

Claude Code Plugin In Testing

What it catches

Automated enforcement so you don't have to remember the rules

Missing budget configuration

Hooks warn when you commit a Worker without budget thresholds configured. No more deploying unprotected handlers.

Catch budget configuration gaps before they reach production

Unsafe binding patterns

Rules flag raw binding access outside withFeatureBudget wrappers, unbounded D1 write loops, and missing circuit breaker error handling.

Get warned about unsafe D1 write patterns during development

Integration drift

Session-start hooks scan for unwrapped fetch/cron/queue handlers. Detects when wrangler.toml, budgets.yaml, or SDK versions fall out of sync.

Run a full platform health check with one slash command

Pre-deploy safety gates

Deploy hooks verify binding presence, observability configuration, and budget thresholds before any push to production.

See cost projections before deploying new features

What Platform SDK Plugin includes

  • 4 slash commands

    /platform-audit scores your project against a 100-point rubric. /platform-integrate guides new SDK setup. /platform-health runs end-to-end checks. /platform-costs analyses spending patterns.

  • Always-active rules

    Three rules (~1.9KB total) loaded into every prompt — SDK wrapper requirements, cost-safety patterns, and wrangler binding validation.

  • 14 on-demand skills

    Consumer SDK integration, admin scaffolding, circuit breaker configuration, resilience patterns, service communication, Hono middleware, and more — loaded only when needed.

  • 9 automated hooks

    Fire on git commits, file writes, and deploy commands. Post-write hooks catch SDK wrapper omissions immediately. Pre-deploy hooks gate on binding and observability config.

  • 100-point audit rubric

    Weighted scoring across SDK integration (30%), observability (25%), cost protection (25%), and security (20%). Concrete numbers, not vague best practices.

  • Companion to Platform SDKs

    The SDKs protect at runtime — circuit breakers, budget enforcement, anomaly detection. The plugin protects during development — catching the mistakes that would bypass those protections.

How it works

Rules run on every prompt. Skills load when you need them. Hooks fire automatically.

3 always-active rules (~1.9KB)
14 on-demand skills (~50KB)
4 autonomous agents
9 automated hooks
What exactly does it access?

What it accesses

  • Your local codebase (wrangler.toml, budgets.yaml, Worker source files)
  • Platform SDK configuration and budget thresholds

Where it stores

  • Nothing — pure Claude Code plugin with no persistent storage

Uninstall with /plugin uninstall platform-sdk@lba-plugins

Network calls

  • None — all rules, skills, agents, and hooks run locally inside Claude Code

Uninstall the plugin to disable

Get notified when Platform SDK Plugin is ready

Leave your details and I'll let you know when it's available.

No spam, ever. Privacy Policy

"After building Platform SDKs, I kept making the same mistakes — deploying Workers without budget thresholds, forgetting to wrap new bindings in withFeatureBudget, letting configuration drift between environments."

Nathan
N
Nathan

Questions about Platform SDK Plugin

What is the Platform SDK Plugin?
A Claude Code plugin that enforces Platform SDK best practices, cost safety rules, and integration standards for Cloudflare Workers projects. It includes 3 always-active rules, 14 on-demand skills, 4 autonomous agents, 9 automated hooks, and 4 slash commands.
How is this different from Platform SDKs?
Platform SDKs are npm packages you install in your Cloudflare Workers — they provide the runtime circuit breakers, budget enforcement, and telemetry. The Platform SDK Plugin is a Claude Code plugin that enforces correct usage of those SDKs during development — it catches mistakes before they reach production.
Does this work with other AI coding tools?
The plugin is built for Claude Code. It uses Claude Code's native plugin system (rules, skills, agents, hooks) which isn't available in other tools. The repo includes an AGENTS.md file that provides a condensed standalone reference for other AI coding tools like Cursor, Codex CLI, or Windsurf.
Do I need Platform SDKs installed first?
Yes. The plugin is a companion to Platform SDKs — it enforces correct usage of the SDKs in your Cloudflare Workers project. Install Platform SDKs first, then add the plugin for automated enforcement during development.
What does the 100-point audit check?
Four weighted categories: SDK integration (30%) checks wrapper coverage and handler protection. Observability (25%) checks logging, tracing, and error collection. Cost protection (25%) checks budgets, circuit breakers, and anomaly thresholds. Security (20%) checks binding access patterns and configuration safety.
What was the $4,868 billing incident?
An infinite D1 write loop ran for four days in January 2026, writing 4.8 billion rows. Platform SDKs prevent it at runtime with circuit breakers. The plugin prevents it during development by catching unsafe patterns before you deploy.
Is this free?
Yes. MIT licenced, fully open source. The plugin runs entirely inside Claude Code with no external dependencies or API calls.
How do I automate Cloudflare Workers cost protection?
Install Platform SDKs for runtime protection (circuit breakers, budget enforcement, anomaly detection), then add the Platform SDK Plugin to Claude Code for development-time enforcement (rules, hooks, agents that catch cost risks before deployment).

SDK + Plugin: the full picture

  • Platform SDKs protect at runtime — circuit breakers trip when budgets are exceeded. The plugin protects during development — hooks catch missing budgets before you deploy.
  • Instead of remembering to configure budget thresholds for every new feature, hooks check automatically on every commit.
  • Instead of manually auditing SDK integration when adding Workers, run /platform-audit and get a scored report.
  • Instead of discovering health check failures in production, /platform-health validates both control and data planes from your terminal.