Borrowing it
Nothing to install: this file belongs to racecraft-lab/racecraft-plugins-public. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/racecraft-lab/racecraft-plugins-public/main/.claude/skills/scaffold-skill/SKILL.mdgit clone --depth 1 https://github.com/racecraft-lab/racecraft-plugins-publicWrote 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/racecraft-lab/racecraft-plugins-public/scaffold-skill)<a href="https://agentmods.dev/skills/racecraft-lab/racecraft-plugins-public/scaffold-skill"><img src="https://agentmods.dev/badge/skills/racecraft-lab/racecraft-plugins-public/scaffold-skill/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/racecraft-lab/racecraft-plugins-public/scaffold-skill"><img src="https://agentmods.dev/badge/skills/racecraft-lab/racecraft-plugins-public/scaffold-skill.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.00091 | $0.00575 |
| Opus 5 | $0.00046 | $0.00287 |
| Sonnet 5 | $0.00018 | $0.00115 |
| Haiku 4.5 | $0.00009 | $0.00057 |
Grade A, and why
scaffold-skill 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 10d 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-skill
Scaffolds a new skill in a marketplace plugin. Both user-invocable and Claude-invocable.
Inputs to ask for
- Plugin — which plugin (default:
speckit-pro) - Skill name — kebab-case, e.g.
my-skill - Description — one sentence with concrete trigger phrases (the description is what Claude matches on; vague descriptions = skill never fires)
- Codex mirror — yes/no. If yes, also create under
codex-skills/<name>/SKILL.md - References / scripts — does the skill need supporting files? Default: no (start minimal per CLAUDE.md "Simplest change" rule)
What this creates
<plugin>/skills/<name>/
└── SKILL.md
With frontmatter:
---
name: <name>
description: <description>
license: MIT
---
Optional Codex mirror:
<plugin>/codex-skills/<name>/
└── SKILL.md
Optional references/ and scripts/ subdirs (only if user said yes).
Post-create
Always run from the repository root:
python3 tests/speckit-pro/run-all.py --layer 1
If Codex mirror created, also run:
python3 tests/speckit-pro/layer1-structural/validate-codex-skills.py
If either fails, fix the SKILL.md before reporting success.
What this does NOT do
- Does not touch
marketplace.jsonorrelease-please-config.json(skills don't have their own version; they live inside a plugin) - Does not commit (use
plugin-publishskill for that, or commit manually) - Does not write skill body content — only the frontmatter scaffold. User fills in the body.
Hard rules
- Frontmatter must have at minimum
nameanddescription namein frontmatter must match the directory name- Description must include concrete trigger phrases — not just "Helps with X"
- Codex mirror must have identical
nameto the Claude Code skill
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.
- 10d ago First seen · 69 lines · 91 tokens per session scan A d388186a5b2b
scaffold-skill is a skill published in the GitHub repository racecraft-lab/racecraft-plugins-public (5 stars, last pushed today), licensed MIT. It adds 91 tokens to every session and 575 once invoked, about $0.0005 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
build-executor
Govern implementation from an approved execution contract. Invoke when execution-contract.md is approved and the user wants disciplined build work, TDD execution, or guarded batch-by-batch implementation.
workflow-start
Primary entry point for the spec-superflow state-machine workflow. Invoke when the user is inside an active spec-superflow change directory (look for .spec-superflow.yaml, changes/ /, proposal.md, specs/, design.md, tasks.md, or execution-contract.md) and asks to start, continue, resume, implement, plan, or figure out…
release-archivist
Close out a spec-superflow change with verification, summary, and archive readiness. Invoke when implementation is complete, verification is underway, or the user asks for a final wrap-up.
bug-investigator
Use when encountering any bug, test failure, or unexpected behavior during spec-superflow execution, before proposing fixes. Invoked automatically when build-executor hits a blockage.
contract-builder
Convert approved planning artifacts into an execution contract. Invoke when the user wants to start building, asks to move from planning to implementation, or when execution-contract.md is missing or stale.
spec-writer
Create or refine spec-superflow planning artifacts. Invoke when the change is understood well enough to write proposal.md, specs/, design.md, and tasks.md.