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/swesmith/davila7__claude-code-templates.734b8a50Wrote 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/swesmith/davila7__claude-code-templates.734b8a50/project-setup)<a href="https://agentmods.dev/commands/swesmith/davila7__claude-code-templates.734b8a50/project-setup"><img src="https://agentmods.dev/badge/commands/swesmith/davila7__claude-code-templates.734b8a50/project-setup.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.00000 | $0.01702 |
| Opus 5 | $0.00000 | $0.00851 |
| Sonnet 5 | $0.00000 | $0.00340 |
| Haiku 4.5 | $0.00000 | $0.00170 |
Grade C, and why
project-setup scanned grade C with 1 finding 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 6d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
"clean": "rm -rf dist/" This is a copy
100% identical to project-setup — 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 — 316 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Setup Helper
Set up new projects with proper structure and best practices.
Purpose
This command helps you set up new projects with proper directory structure, configuration files, and development environment.
Usage
/project-setup
What this command does
- Creates project structure with standard directories
- Sets up configuration files (.gitignore, README, etc.)
- Initializes version control and development tools
- Configures environment files and dependencies
- Follows language-specific conventions and best practices
Project Structure Templates
Generic Project Structure
project-name/
├── README.md # Project documentation
├── .gitignore # Git ignore rules
├── .env.example # Environment variables template
├── LICENSE # Project license
├── CHANGELOG.md # Version history
├── docs/ # Documentation
│ ├── API.md
│ ├── CONTRIBUTING.md
│ └── DEPLOYMENT.md
├── src/ # Source code
│ ├── main/
│ ├── utils/
│ └── config/
├── tests/ # Test files
│ ├── unit/
│ ├── integration/
│ └── fixtures/
├── scripts/ # Build and deployment scripts
│ ├── build.sh
│ ├── deploy.sh
│ └── setup.sh
└── config/ # Configuration files
├── development.yml
├── production.yml
└── testing.yml
Web Application Structure
web-app/
├── public/ # Static assets
│ ├── index.html
│ ├── favicon.ico
│ └── assets/
│ ├── css/
│ ├── js/
│ └── images/
├── src/ # Source code
│ ├── components/ # Reusable components
│ ├── pages/ # Page components
│ ├── services/ # API services
│ ├── utils/ # Utility functions
│ ├── styles/ # Stylesheets
│ └── config/ # Configuration
├── tests/ # Test files
└── build/ # Build output
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.
- 6d ago First seen · 316 lines · 0 tokens per session scan C be0f448848b0
project-setup is a command published in the GitHub repository swesmith/davila7__claude-code-templates.734b8a50 (2 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,702 tokens. A static security scan graded it C with 1 finding (recursive force delete). It is 100% identical to project-setup, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
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.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.