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 patricio0312rev/skillset --skill project-scaffoldergit clone --depth 1 https://github.com/patricio0312rev/skillsetWrote 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/patricio0312rev/skillset/project-scaffolder)<a href="https://agentmods.dev/skills/patricio0312rev/skillset/project-scaffolder"><img src="https://agentmods.dev/badge/skills/patricio0312rev/skillset/project-scaffolder/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/patricio0312rev/skillset/project-scaffolder"><img src="https://agentmods.dev/badge/skills/patricio0312rev/skillset/project-scaffolder.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.00080 | $0.00602 |
| Opus 5 | $0.00040 | $0.00301 |
| Sonnet 5 | $0.00016 | $0.00120 |
| Haiku 4.5 | $0.00008 | $0.00060 |
Grade A, and why
project-scaffolder 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 9d 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.
This is a copy
100% identical to project-scaffolder — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Scaffolder
Generate production-ready starter repositories with best-practice conventions for any tech stack.
Core Workflow
- Determine stack: Ask user to specify or infer from context (Next.js, Vite, Nest, FastAPI, etc.)
- Select template: Use references/templates.md to choose the appropriate project structure
- Generate structure: Create complete folder tree with all necessary files
- Add baseline code: Include working "hello world" route/page as proof of concept
- Configure tooling: Add package.json/requirements.txt, tsconfig, linting, formatting configs
- Create scripts: Include dev, build, test, and deployment scripts
- Document setup: Generate comprehensive README with setup steps and next actions
Key Deliverables
Every scaffolded project must include:
- Folder tree: Well-organized src/, lib/, config/, tests/ structure
- Baseline code: Working hello world endpoint or page
- Package files: package.json, requirements.txt, Cargo.toml, etc.
- Configs: TypeScript, ESLint, Prettier, environment files (.env.example)
- Scripts: npm scripts or Makefile for common tasks
- README: Setup instructions, tech stack overview, next steps
- Git setup: .gitignore configured for the stack
Stack-Specific Patterns
See references/templates.md for detailed patterns per stack:
- Next.js App Router
- Vite + React
- NestJS
- FastAPI
- Express + TypeScript
- Vue + Vite
- SvelteKit
Best Practices
- Use absolute imports (@/ alias) where supported
- Include environment variable templates
- Add basic error handling and logging setup
- Configure path mappings in tsconfig
- Include Docker files for containerization (optional)
- Add GitHub Actions or CI workflow templates (optional)
Progressive Enhancement
Start with minimal viable structure, then add:
- Database setup (Prisma, TypeORM, SQLAlchemy)
- Auth scaffolding (NextAuth, Passport, JWT)
- API client setup (Axios, Fetch wrapper)
- State management (Zustand, Redux, Pinia)
- Testing setup (Jest, Vitest, Pytest)
What ships with it
1 file 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.
- 9d ago First seen · 66 lines · 80 tokens per session scan A b7db080ad1ea
project-scaffolder is a skill published in the GitHub repository patricio0312rev/skillset (6 stars, last pushed 8mo ago), licensed MIT. It adds 80 tokens to every session and 602 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to project-scaffolder, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…