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 agentmods add commands/matteocervelli/llms/project-creategit clone --depth 1 https://github.com/matteocervelli/llmsWhat 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 | $0.00008 | $0.01025 |
| Opus 5 | $0.00004 | $0.00513 |
| Sonnet 5 | $0.00002 | $0.00205 |
| Haiku 4.5 | $0.00001 | $0.00103 |
Grade A, and why
project-create 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 today.
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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Kickoff: $ARGUMENTS
💡 Tip: For safer planning, activate Plan Mode (press Shift+Tab twice) before running this command to review the project structure before creation.
Repository Setup
# Create project structure
!mkdir -p $ARGUMENTS/{docs/{architecture,guides,implementation,PRD},src,tests,.github/workflows}
!cd $ARGUMENTS
# Initialize Git and GitHub
!git init
!gh repo create $ARGUMENTS --private --description="[Project description]"
!git remote add origin https://github.com/$(gh api user --jq .login)/$ARGUMENTS.git
Core Documentation
Create essential planning documents:
1. Planning (docs/PLANNING.md)
- Goals & Objectives: Primary/secondary goals with success metrics
- Use Cases: 4+ core use cases with inputs/outputs
- Technical Assumptions: Infrastructure, data volume, integrations
- Security Requirements: Authentication, data protection, compliance needs
2. Roadmap (docs/ROADMAP.md)
- Phases: MVP → Enhancement → Advanced → Scale
- Timeline: Milestone dates and deliverables
- Security & Privacy: GDPR, data protection strategy
- Success Criteria: Measurable acceptance criteria
3. Architecture (docs/architecture/ARCHITECTURE.md)
- Pattern: MVC/Microservices/JAMstack decision
- Components: System diagram and data flow
- Security Architecture: Auth flow, data protection
- Performance Strategy: Caching, scaling, optimization
4. Tech Stack (docs/architecture/TECH-STACK.md)
- Backend/Frontend/Database: Technology choices with rationale
- DevOps Tools: CI/CD, monitoring, deployment
- Security Tools: SAST/DAST, dependency scanning
- Development Workflow: Commands and setup instructions
Environment Configuration
# Create environment files
!touch .env.example .env .gitignore
!echo "# Environment variables\n.env\n.env.local\n\n# Dependencies\nnode_modules/\n__pycache__/\n\n# Build outputs\ndist/\nbuild/\n*.log" > .gitignore
Quality & Security Setup
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.
- today First seen · 142 lines · 8 tokens per session scan A 1640f54f4927
project-create is a command published in the GitHub repository matteocervelli/llms (25 stars, last pushed 3mo ago), licensed MIT. It adds 8 tokens to every session and 1,025 once invoked, about $0.0000 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-01.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.