Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add robzilla1738/roberts-skills/plugin install scaffoldWrote 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/commands/robzilla1738/roberts-skills/scaffold)<a href="https://agentmods.dev/commands/robzilla1738/roberts-skills/scaffold"><img src="https://agentmods.dev/badge/commands/robzilla1738/roberts-skills/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/commands/robzilla1738/roberts-skills/scaffold"><img src="https://agentmods.dev/badge/commands/robzilla1738/roberts-skills/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.00033 | $0.00200 |
| Opus 5.5 | $0.00013 | $0.00080 |
| Sonnet 5.5 | $0.00007 | $0.00040 |
| Haiku 4.5 | $0.00003 | $0.00020 |
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 2mo 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 or extend a project: $ARGUMENTS
Load and follow the scaffold skill at ${CLAUDE_PLUGIN_ROOT}/skills/scaffold/SKILL.md:
start with product intake to pick the right profile, then build boring infrastructure first
(typed env, errors, tests, install, lint, build, database, API route, optional auth) before
any product features. Install every intake-selected add-on (AI SDK, Resend, Stripe, Sentry,
PostHog) in the integrations phase — never leave them README-only. Follow the phase bundle
and the verification checklist; record the scaffold profile, installed add-ons, and
production-habits checklist in the README.
If $ARGUMENTS is empty, run product intake to learn what's being built.
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.
- 2mo ago First seen · 16 lines · 33 tokens per session scan A 6d2cf7f30ba1
scaffold is a command published in the GitHub repository robzilla1738/roberts-skills (4 stars, last pushed 4mo ago), licensed MIT. It adds 33 tokens to every session and 200 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.
Other commands, from other repositories
hatch3r-project-spec
Translate a greenfield vision into future-state design artifacts -- ADRs, domain model, API contracts, per-module technical specs, and a board-ready todo.md.
hatch3r-api-spec
Generate or validate an OpenAPI specification from the codebase. Scans route definitions, extracts schemas, and produces a complete API spec.
hatch3r-design-system-create
Create a project design system from brand assets or an elicitation dialog — DTCG 2025.10 token emission, 3-tier taxonomy (primitive → semantic → component), OKLCH ramps, dual output design.md + design-tokens.json, gated on WCAG 2.2 AA contrast, 100% theme parity, and 0 dangling aliases.
auth-implementation
Use when a project needs real working login and signup rather than advice. Wiring up Clerk or Supabase Auth, protecting routes, handling sessions. Writes actual code, not guidance.
hatch3r-auth-scaffold
Scaffold authentication boilerplate for a greenfield API service — OAuth 2.1 authorization-code-with-PKCE flow, OIDC ID-token validation, and hashed personal-access-token (PAT) issuance/verification. Implementer writes the code; hatch3r-security gates it against the CQ3 auth-depth floor.
api
Design REST endpoints with consistent error envelopes, versioning, pagination, and idempotency.