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.
git clone --depth 1 https://github.com/TheBeardedBearSAS/claude-craftWrote 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/thebeardedbearsas/claude-craft/scaffold-project)<a href="https://agentmods.dev/commands/thebeardedbearsas/claude-craft/scaffold-project"><img src="https://agentmods.dev/badge/commands/thebeardedbearsas/claude-craft/scaffold-project.svg" alt="Measured on agentmods" 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.00020 | $0.01246 |
| Opus 5 | $0.00010 | $0.00623 |
| Sonnet 5 | $0.00004 | $0.00249 |
| Haiku 4.5 | $0.00002 | $0.00125 |
Grade A, and why
scaffold-project 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scaffold Vite Project
You are an expert Vite build engineer. Vite has no component model of its own — the closest analog to "generate a component" is scaffolding a new project from an official template, or generating a library skeleton wired for build.lib + vite-plugin-dts.
Scope framework-agnostic uniquement. Pour Vite en tant que dev-server React/Vue/Angular/Svelte, voir le tooling.md de ce stack.
ARGUMENTS
$ARGUMENTS
project-name: Directory/package name for the new project (kebab-case)--template=<template>:vanilla-ts(default) orlit-ts--lib: Scaffold a publishable library skeleton instead of an app (addsbuild.lib+vite-plugin-dts)
MISSION
- Run
npm create vite@latestnon-interactively with the requested template - Install dependencies
- If
--libis passed, rewritevite.config.tsfor library mode and addvite-plugin-dts - Add a minimal Vitest setup
- Report the created structure and next steps
APP SCAFFOLD (default)
# Vanilla TypeScript SPA
npm create vite@latest <project-name> -- --template vanilla-ts
# Lit + TypeScript (Web Components, still framework-agnostic — no app framework runtime)
npm create vite@latest <project-name> -- --template lit-ts
cd <project-name>
npm install
Resulting Structure (vanilla-ts)
<project-name>/
├── index.html
├── package.json
├── tsconfig.json
├── vite.config.ts # generated by scaffold-project when --lib is not set; add manually otherwise
├── public/
│ └── vite.svg
└── src/
├── main.ts
├── style.css
├── counter.ts
└── typescript.svg
LIBRARY SCAFFOLD (--lib)
Start from vanilla-ts, then add library-mode config:
npm create vite@latest <project-name> -- --template vanilla-ts
cd <project-name>
npm install
npm install -D vite-plugin-dts
// vite.config.ts
import { defineConfig } from 'vite'
import dts from 'vite-plugin-dts'
export default defineConfig({
plugins: [
dts({
include: ['src'],
rollupTypes: true,
}),
],
build: {
lib: {
entry: 'src/index.ts',
name: 'MyLib',
formats: ['es', 'cjs'],
fileName: (format) => `my-lib.${format === 'es' ? 'js' : 'cjs'}`,
},
rollupOptions: {
// Externalize peer dependencies that consumers must provide
external: [],
},
},
})
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.
- 4d ago First seen · 179 lines · 20 tokens per session scan A 715103ad2ba1
scaffold-project is a command published in the GitHub repository TheBeardedBearSAS/claude-craft (105 stars, last pushed 5d ago), licensed MIT. It adds 20 tokens to every session and 1,246 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-09-03.
Other commands, from other repositories
svelte:component
Create new Svelte components with best practices, proper structure, and optional TypeScript support.
pn-audit-layout
Surgical frontend layout audit — spacing tokens, grid consistency, component rhythm, and responsive behavior. Standalone or chained by pn-frontend-audit.
init
Set up Hono-based type-safe IPC architecture for Electron.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.