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.
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.
Unsafe binding patterns
Rules flag raw binding access outside withFeatureBudget wrappers, unbounded D1 write loops, and missing circuit breaker error handling.
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.
Pre-deploy safety gates
Deploy hooks verify binding presence, observability configuration, and budget thresholds before any push to production.
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.
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."
Questions about Platform SDK Plugin
What is the Platform SDK Plugin?
How is this different from Platform SDKs?
Does this work with other AI coding tools?
Do I need Platform SDKs installed first?
What does the 100-point audit check?
What was the $4,868 billing incident?
Is this free?
How do I automate Cloudflare Workers cost protection?
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.
Also by Little Bear Apps