What is worker-backend?

A set of procedures for changing the backend of a Cloudflare Worker, a small server-side program that runs on Cloudflare. It covers areas such as authentication, request checks, API keys, Stripe billing, database changes, and API endpoints.

Use it to modify the listed Cloudflare Worker features, update its database schema, add validation, and test request-and-response behavior.

It gives backend changes a defined process, including writing tests first. This helps catch incorrect success and error behavior before changes are finished.

worker-backend — Skill for Claude Code and Codex by bierlingm: A set of procedures for changing the backend of…

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.

agentmods

npx agentmods add skills/bierlingm/spikes/worker-backend

Any agent

npx skills add bierlingm/spikes --skill worker-backend

Clone the repo

git clone --depth 1 https://github.com/bierlingm/spikes

Made for: Claude Code, Codex.

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/skills/bierlingm/spikes/worker-backend.svg)](https://agentmods.dev/skills/bierlingm/spikes/worker-backend)

Your own site

<a href="https://agentmods.dev/skills/bierlingm/spikes/worker-backend"><img src="https://agentmods.dev/badge/skills/bierlingm/spikes/worker-backend.svg" alt="Measured on agentmods" height="20"></a>

Per session 30 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

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

Security scan A 1 finding. Scan, not verified.

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	$0.00030	$0.01301
Opus 5	$0.00015	$0.00651
Sonnet 5	$0.00006	$0.00260
Haiku 4.5	$0.00003	$0.00130

Measured 3d ago against content hash 3c427f628e25, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

worker-backend scanned grade A with 1 finding 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 3d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

8. **Manually verify via wrangler dev.** Start `cd ../spikes-hosted/worker && npx wrangler dev --port 8787` and test the endpoint with curl. Verify the happy path and at least one error path.

.factory/skills/worker-backend/SKILL.md · 87 lines

How it starts

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

Backend Worker

NOTE: Startup and cleanup are handled by worker-base. This skill defines the WORK PROCEDURE.

When to Use This Skill

Features that modify the Cloudflare Worker backend at ../spikes-hosted/worker/. This includes:

API key system (creation, revocation, scoping, auth middleware)
Stripe metered billing (meters, meter events, budget enforcement)
Authentication endpoints
Stripe webhook handling (agent tier lifecycle)
Database schema changes (migrations)
API endpoint changes
Request validation (Zod schemas)

Work Procedure

Read the feature description thoroughly. Understand preconditions and expected behavior.
Understand current code. Read relevant source files in ../spikes-hosted/worker/src/. The worker may be a single index.ts (early milestones) or modularized (later milestones). Read schema.sql and any migrations to understand the database.
Write tests FIRST (TDD). Create test files in ../spikes-hosted/worker/test/ using Vitest + Miniflare patterns:
- Import env from cloudflare:test
- Use SELF.fetch() to test request/response cycles
- Seed D1 data in beforeEach
- Test both success and error paths
- Run tests: cd ../spikes-hosted/worker && npx vitest run — they MUST fail (red phase)
Write database migrations if needed. Create numbered migration files in ../spikes-hosted/worker/migrations/. Migration names should be descriptive (e.g., 002_add_rate_limits_table.sql).
Implement the feature. Make the tests pass (green phase). Follow existing patterns in the codebase. If modularizing, create new files in src/handlers/, src/middleware/, src/db/, or src/utils/.
Run all tests. cd ../spikes-hosted/worker && npx vitest run — all tests must pass (not just new ones).
Run typecheck. cd ../spikes-hosted/worker && npx tsc --noEmit — must pass with zero errors.
Manually verify via wrangler dev. Start cd ../spikes-hosted/worker && npx wrangler dev --port 8787 and test the endpoint with curl. Verify the happy path and at least one error path.

Read the full file on GitHub · 87 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.

3d ago First seen · 87 lines · 30 tokens per session scan A 3c427f628e25

Subscribe to this mod's changes

worker-backend is a skill published in the GitHub repository bierlingm/spikes (1 stars, last pushed 1mo ago), licensed MIT. It adds 30 tokens to every session and 1,301 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Backend and APIs Security

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

worker-backend