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 fltman/project-scaffolder --skill project-setupgit clone --depth 1 https://github.com/fltman/project-scaffolderWrote 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/fltman/project-scaffolder/project-setup)<a href="https://agentmods.dev/skills/fltman/project-scaffolder/project-setup"><img src="https://agentmods.dev/badge/skills/fltman/project-scaffolder/project-setup/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/fltman/project-scaffolder/project-setup"><img src="https://agentmods.dev/badge/skills/fltman/project-scaffolder/project-setup.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.00022 | $0.00913 |
| Opus 5.5 | $0.00009 | $0.00365 |
| Sonnet 5.5 | $0.00004 | $0.00183 |
| Haiku 4.5 | $0.00002 | $0.00091 |
Grade A, and why
project-setup 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.
How it starts
The opening of the file, as written. The whole thing — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Setup Skill
When to Use This Skill
Activate this skill when:
- User asks to "set up a new project"
- User asks to "create a CLAUDE.md"
- User asks to "initialize Claude Code" for a project
- User asks to "scaffold" a project
- User wants to add Claude Code support to existing code
Do NOT use for:
- General coding questions
- Editing existing CLAUDE.md (see optimize-claude-md skill)
- Running or testing projects
Prerequisites
- Write access to target directory
- For existing projects: ability to read config files (package.json, pyproject.toml, etc.)
Instructions
Step 1: Determine Project Type
Analyze the target directory:
# Check for Node.js/TypeScript
ls package.json 2>/dev/null && echo "Node.js project"
# Check for Python
ls pyproject.toml requirements.txt setup.py 2>/dev/null && echo "Python project"
# Check for Go
ls go.mod 2>/dev/null && echo "Go project"
# Check for Rust
ls Cargo.toml 2>/dev/null && echo "Rust project"
If no config files exist, ask the user what type of project they want to create.
Step 2: Gather Project Information
For new projects, ask:
- Project name
- Project description
- Primary language/framework
- Any special requirements
For existing projects, extract from:
- README.md (description)
- Package config (dependencies, scripts)
- Existing folder structure
Step 3: Generate CLAUDE.md
Use the appropriate template:
- React/TypeScript →
/templates/claude-md/react-typescript.md - Python API →
/templates/claude-md/python-api.md - Full Stack →
/templates/claude-md/fullstack.md - Other →
/templates/claude-md/minimal.md
Fill in all {{PLACEHOLDER}} values with actual project information.
Step 4: Create Slash Commands
Set up .claude/commands/ with useful commands:
Essential commands:
review.md- Code reviewtest-and-commit.md- Quality check and commit
Copy from /templates/commands/ and customize.
Step 5: Verify Setup
- Ensure CLAUDE.md is valid markdown
- Check that referenced commands/paths exist
- Test that any scripts are 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.
- 2mo ago First seen · 144 lines · 22 tokens per session scan A 12239f161e60
project-setup is a skill published in the GitHub repository fltman/project-scaffolder (88 stars, last pushed 11d ago), licensed MIT. It adds 22 tokens to every session and 913 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-30.
project-setup compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| project-setupfltman/project-scaffolder | Skill | 88 | 11d ago | MIT | A | 22 | Claude Code, Codex |
| imagegenopenai/codex | Skill | 134k | today | Apache-2.0 | A | 113 | Codex |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | 2d ago | MIT | A | 200 | Claude Code, Codex |
| playwright-climicrosoft/playwright | Skill | 100k | 2d ago | Apache-2.0 | A | 19 | Claude Code |
| browser-automationopenclaw/openclaw | Skill | 394k | yesterday | MIT | A | 36 | Claude Code |
| systematic-debuggingobra/superpowers | Skill | 315k | 5d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | yesterday | MIT | A | 95 | Claude Code |