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.
npx skills add starman69/claude-workshops --skill aftergit clone --depth 1 https://github.com/starman69/claude-workshopsWrote 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.
[](https://agentmods.dev/skills/starman69/claude-workshops/after)<a href="https://agentmods.dev/skills/starman69/claude-workshops/after"><img src="https://agentmods.dev/badge/skills/starman69/claude-workshops/after/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.
<a href="https://agentmods.dev/skills/starman69/claude-workshops/after"><img src="https://agentmods.dev/badge/skills/starman69/claude-workshops/after.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.1 | $0.00047 | $0.00450 |
| Opus 5 | $0.00023 | $0.00225 |
| Sonnet 5 | $0.00009 | $0.00090 |
| Haiku 4.5 | $0.00005 | $0.00045 |
Grade A, and why
scaffold-feature 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 8d 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.
What it actually says
scaffold-feature
When to use
- User asks to add a new feature to TodoMVC (e.g., "add a dark mode toggle", "add a due-date field")
- No existing component owns the feature already (check
src/components/first)
What it does
Generates three artifacts in the TodoMVC checkout:
src/components/<FeatureName>.tsx— React component, function declaration, typed props, default exportsrc/components/<FeatureName>.test.tsx— React Testing Library tests (render + one primary interaction)- Wiring — import + mount in the nearest parent (
src/App.tsxor closest container) at an appropriate slot
Steps
- Read
CLAUDE.mdfor stack + convention details. - Parse the user's feature request into:
FeatureName(PascalCase), one-line purpose, visible affordance. - Generate the component — idiomatic React per the project's conventions.
- Generate tests — render without crashing + primary interaction works.
- Edit the nearest parent to import + mount the component.
- Run
npm test -- --watchAll=false. Report pass/fail.
Conventions (TodoMVC-specific)
- Components: PascalCase,
.tsx, function declaration (not arrow), default export - Tests: co-located,
*.test.tsx, React Testing Library - State: local
useState/useReducer; do not introduce Redux - No new dependencies without asking
- Do not modify the spec-test suite
Supporting files
scripts/scaffold-feature.sh— optional helper that creates empty file skeletons before Claude fills them. Safe to skip; Skill can generate files directly.
Do not
- Touch
node_modules/,build/,dist/, snapshot files - Rename anything outside the new component's scope
- Add router routes unless explicitly asked
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 47 lines · 47 tokens per session scan A 1baac0687b1a
scaffold-feature is a skill published in the GitHub repository starman69/claude-workshops (2 stars, last pushed 4mo ago), licensed MIT. It adds 47 tokens to every session and 450 once invoked, about $0.0002 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.
Other skills, from other repositories
react-patterns
React 18/19 patterns including hooks discipline, server/client component boundaries, Suspense + error boundaries, form actions, data fetching, state management decision trees, and accessibility-first composition. Use when writing or reviewing React components.
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
material-ui-tailwind
Integrates Material UI with Tailwind CSS v4 using cascade layers (enableCssLayer, @layer order) and documents Tailwind v3 interoperability (preflight, important, injectFirst, portals). Use when combining MUI with Tailwind utilities, slotProps className, or theme token bridges.
r3f-best-practices
React Three Fiber (R3F) and Poimandres ecosystem best practices. Use when writing, reviewing, or optimizing R3F code. Triggers on tasks involving @react-three/fiber, @react-three/drei, zustand, @react-three/postprocessing, @react-three/rapier, or leva.
dashboard-widgets
Author a dashboard widget — a small React component backed by named LangWatchQL queries — from a plain question. Discovers the analytics schema, writes the queries, writes the widget file, saves it, then proves it renders. Use when asked to build, prototype, or iterate on a custom chart widget, or to add a widget…
assistant-ui-primitives
Guide for assistant-ui UI primitives - ThreadPrimitive, ComposerPrimitive, MessagePrimitive. Use when customizing chat UI components.