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 FlorianBruniaux/claude-code-plugins --skill scaffoldgit clone --depth 1 https://github.com/FlorianBruniaux/claude-code-pluginsWrote 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/florianbruniaux/claude-code-plugins/scaffold)<a href="https://agentmods.dev/skills/florianbruniaux/claude-code-plugins/scaffold"><img src="https://agentmods.dev/badge/skills/florianbruniaux/claude-code-plugins/scaffold/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/florianbruniaux/claude-code-plugins/scaffold"><img src="https://agentmods.dev/badge/skills/florianbruniaux/claude-code-plugins/scaffold.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.00052 | $0.02371 |
| Opus 5.5 | $0.00021 | $0.00948 |
| Sonnet 5.5 | $0.00010 | $0.00474 |
| Haiku 4.5 | $0.00005 | $0.00237 |
Grade A, and why
scaffold 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 today.
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.
How it starts
The opening of the file, as written. The whole thing — 404 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code scaffold coach
Interactive wizard that identifies the right Claude Code component for your use case and generates a ready-to-use template.
Usage: /scaffold (no arguments needed). Start the conversation.
Phase 1: Discovery
Open with this prompt, then wait for the user's answer before asking anything else:
What do you want to automate or build? One sentence is enough to start.
Once you have a rough idea, ask the following questions in order. Skip a question if a previous answer already answers it.
Q1: Trigger
How is this triggered?
a) I run it myself with a command (e.g.
/something) b) It should fire automatically when Claude takes an action (writes a file, runs bash, finishes a session...) c) It should apply all the time, every session, without me doing anything
- If b → likely a Hook (jump to Q_hook)
- If c → likely a Rule (jump to Q_rule)
- If a → continue with Q2
Q2: Domain expertise
Does this require deep, project-specific expertise? For example: knowing your GraphQL schema, your migration conventions, your internal API patterns, your cost model...
- If yes, deep expertise → likely an Agent (jump to Q_agent)
- If no, more of a checklist or procedure → continue with Q3
Q3: Complexity
How much context and logic does this involve?
a) A lot: multiple rules, domain-specific examples, nuanced judgment b) Straightforward: a few steps, a template, some bash
- If a → likely a Skill
- If b → likely a Command
Q4: Reuse scope
Who needs this?
a) Just me b) My whole team c) It needs to be invokable by other agents automatically
- c → strengthens Agent (needs a
description:field that other agents can read) - b → strengthens Command or Skill (shared config)
- a → can stay a simple personal Command
Q5: Output type
What should happen at the end?
a) A report or analysis: Claude reads and explains, no files touched b) Code or files generated c) An action taken (commit, push, API call...) d) Claude's behavior changes permanently (always does X, never does Y)
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.
- today First seen · 404 lines · 52 tokens per session scan A 892451fc3ec0
scaffold is a skill published in the GitHub repository FlorianBruniaux/claude-code-plugins (43 stars, last pushed yesterday), licensed MIT. It adds 52 tokens to every session and 2,371 once invoked, about $0.0002 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-10-29.
Other skills, from other repositories
app-store-screenshots
Use when building App Store or Google Play screenshot pages, generating exportable marketing screenshots for iOS and/or Android apps, or creating programmatic screenshot generators with Next.js. Triggers on app store, play store, screenshots, marketing assets, html-to-image, phone mockup, android screenshots, feature…
content
Content production and SEO writing skills. Blog posts, long-form content research, structured content frameworks, audience-targeted writing, content optimization. Triggers on: blog, content writing, article, copywriting, content strategy, content brief, SEO content, audience research.
expo-app-config
Choosing between app.json vs app.config.ts vs app.config.js, environment variables, variants, extra fields, plugin chain, and slug/scheme/bundle/version discipline. Triggers on app.json, app.config.ts, app.config.js, expo config, environment variable, .env, eas secret, variant, extra field, slug, scheme, bundle…
expo-modules
Writing Swift/Kotlin native modules with the Expo Modules API, requireNativeModule, async functions, view modules, and the event-emitter pattern. Triggers on expo modules, native module, swift, kotlin, requireNativeModule, expo-module-scripts, expo.modules.json, view module, event emitter, native function, async…
expo-notifications
Push and local notification setup with expo-notifications. iOS (APNs) + Android (FCM) credentials, permission flow, channels (Android 8+), categories, and scheduled notifications.
expo-config-plugin
Writing Expo config plugins, withInfoPlist, withAndroidManifest, withDangerousMod, mod compose, plugin testing, and registration in app.config.ts. Triggers on config plugin, with-plugin, withInfoPlist, withAndroidManifest, withDangerousMod, withEntitlementsPlist, withGradleProperties, mod, native config, expo plugin…