agentmods.dev

worker-fullstack

worker-fullstack is a skill for Claude Code, Codex from bierlingm/spikes. It costs 21 tokens per session (1,150 once invoked), scanned A, original, MIT.

A workflow skill for changes that span a website and its related repository, such as widgets, documentation, packages, registries, or deployment automation. It includes procedures for keeping copies synchronized, checking file size, validating workflows, and testing changes.

In plain words
What is it for?
Use it for widget updates, site-content files, npm packages, registry manifests, documentation, CI/CD workflows, or other changes touching both repositories.
Why use it?
It coordinates work across repositories and reduces the chance that a source file, published copy, documentation page, or CI configuration becomes inconsistent. It also defines checks for the affected parts.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is "whatWasImplemented": "Test infrastructure in ../spikes-hosted/worker/: vitest.config.ts with defineWorkersConfig, tsconfig.json with strict mode and workers ty.

not rated 1repo 4d ago A scan 21 tokens original MIT

Good fit Use it for widget updates, site-content files, npm packages, registry manifests, documentation, CI/CD workflows, or other changes touching both repositories.

Compare 6 skills from other repositories ↓
View source ↗ bierlingm/spikes
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/bierlingm/spikes
agentmods
npx agentmods add skills/bierlingm/spikes/worker-fullstack

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.

agentmods badge for worker-fullstack

README.md
[![agentmods](https://agentmods.dev/badge/skills/bierlingm/spikes/worker-fullstack/github.svg)](https://agentmods.dev/skills/bierlingm/spikes/worker-fullstack)
Your own site
<a href="https://agentmods.dev/skills/bierlingm/spikes/worker-fullstack"><img src="https://agentmods.dev/badge/skills/bierlingm/spikes/worker-fullstack/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.

agentmods 80×15 button for worker-fullstack

Your own site · 80×15
<a href="https://agentmods.dev/skills/bierlingm/spikes/worker-fullstack"><img src="https://agentmods.dev/badge/skills/bierlingm/spikes/worker-fullstack.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 21 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,150 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00021 $0.01150
Opus 5.5 $0.00008 $0.00460
Sonnet 5.5 $0.00004 $0.00230
Haiku 4.5 $0.00002 $0.00115

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

Security

Grade A, and why

worker-fullstack 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.

.factory/skills/worker-fullstack/SKILL.md · 98 lines

How it starts

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

Fullstack Worker

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

When to Use This Skill

Features that touch documentation, site content, npm packages, or span both repos. This includes:

  • Site content (llms.txt, agents.md, llms-full.txt)
  • npm package creation (spikes-mcp wrapper)
  • Registry manifests (smithery.yaml)
  • Documentation updates
  • CI/CD workflow configuration

Work Procedure

  1. Read the feature description thoroughly. Understand what's being changed and in which repo(s).

  2. For widget changes:

    • Read ./widget/spikes.js (the source of truth)
    • Make changes to widget/spikes.js
    • Copy to site/spikes.js (CDN copy) if it exists
    • Verify widget size: gzip -c widget/spikes.js | wc -c — must stay under 15KB
    • Test manually: cd cli && cargo run -- serve --port 3847, open browser, verify behavior
    • Use agent-browser to verify interactive behaviors (toasts, dedup, z-index)

  3. For CI/CD changes:

    • Read existing workflows in .github/workflows/ (both repos)
    • Make changes to workflow YAML files
    • Validate YAML syntax
    • Test locally if possible (e.g., run the test commands that CI would run)

  4. For documentation:

    • Create or update markdown files in ./docs/
    • Ensure all CLI commands are accurate by running spikes <cmd> --help
    • Ensure all widget attributes are accurate by reading widget/spikes.js
    • Cross-reference with actual behavior

  5. For dependency cleanup:

    • Edit cli/Cargo.toml to remove crates
    • Remove all source files that import the removed crates
    • Remove module declarations in mod.rs and main.rs
    • Run cd cli && cargo build — must succeed with no errors or warnings
    • Run cd cli && cargo test — all existing tests must still pass

  6. For test infrastructure:

    • Create vitest.config.ts in ../spikes-hosted/worker/
    • Create tsconfig.json in ../spikes-hosted/worker/
    • Create test helper files in ../spikes-hosted/worker/test/
    • Add dev dependencies to package.json
    • Verify: cd ../spikes-hosted/worker && npx vitest run passes

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

  1. 1mo ago First seen · 98 lines · 21 tokens per session scan A 796a91c7a485

Subscribe to this mod's changes

worker-fullstack is a skill published in the GitHub repository bierlingm/spikes (1 stars, last pushed 4d ago), licensed MIT. It adds 21 tokens to every session and 1,150 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.

Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 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

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…

vercel/next.js · 123 tokens