What is worker-widget?

A work procedure for changing the behavior of a project’s widget and keeping its four copies synchronized. It covers configuration, network requests, error handling, visual indicators, and related documentation.

Implementing widget behavior changes, updating request or configuration handling, adding error indicators or tooltips, and verifying the result in a browser.

It gives widget changes a consistent source of truth and requires planned browser checks for interactive behavior.

worker-widget — Skill for Claude Code and Codex by bierlingm: A work procedure for changing the behavior of a…

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-widget

Any agent

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

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

Your own site

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

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

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

Security scan A 0 findings. 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.00023	$0.01421
Opus 5	$0.00012	$0.00711
Sonnet 5	$0.00005	$0.00284
Haiku 4.5	$0.00002	$0.00142

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

Security

Grade A, and why

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

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-widget/SKILL.md · 95 lines

How it starts

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

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

When to Use This Skill

Features that modify widget behavior (widget/spikes.js), widget config parsing, POST/sync logic, visual indicators, or require syncing the 4 widget copies. Also handles widget-related documentation updates.

Required Skills

agent-browser — for manual verification of widget behavior in the browser. Invoke after implementation to verify interactive behaviors (button appearance, error indicators, tooltips, POST targets).

Work Procedure

Read the feature description thoroughly. Understand the behavioral change and acceptance criteria.
Read the architecture notes:
- .factory/library/architecture.md — especially "Widget Endpoint Resolution" and "Widget Error Visibility" sections
- Current widget source: widget/spikes.js (source of truth)
Write tests first (if applicable).
- This widget has no JS test harness. Instead, plan your manual verification steps BEFORE coding.
- List the specific scenarios you will verify with agent-browser.
Implement the change in widget/spikes.js.
- widget/spikes.js is the SOURCE OF TRUTH. Edit this file first.
- Follow existing patterns: inline styles, no external dependencies, IIFE pattern.
- For config changes: modify the config object initialization (~line 30-35).
- For POST changes: modify saveSpike() (~line 260-295).
- For button changes: modify createButton() and related functions.
Sync all 4 widget copies. After editing widget/spikes.js, copy it to:
- site/spikes.js
- site/widget.js
- cli/assets/spikes.js Verify with: diff widget/spikes.js site/spikes.js && diff widget/spikes.js site/widget.js && diff widget/spikes.js cli/assets/spikes.js
Run automated tests:
- cd cli && cargo test --jobs 5 — all tests must pass
- gzip -c widget/spikes.js | wc -c — must be ≤15,360 bytes (15KB)

Read the full file on GitHub · 95 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 · 95 lines · 23 tokens per session scan A 80ef59f10f5c

Subscribe to this mod's changes

worker-widget is a skill published in the GitHub repository bierlingm/spikes (1 stars, last pushed 1mo ago), licensed MIT. It adds 23 tokens to every session and 1,421 once invoked, about $0.0001 per session on Opus 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.

Frontend

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-widget