Borrowing it
Nothing to install: this file belongs to matteocervelli/llms. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/matteocervelli/llms/main/.claude/skills/project-create/SKILL.mdgit clone --depth 1 https://github.com/matteocervelli/llmsWrote 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/matteocervelli/llms/project-create)<a href="https://agentmods.dev/skills/matteocervelli/llms/project-create"><img src="https://agentmods.dev/badge/skills/matteocervelli/llms/project-create/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/matteocervelli/llms/project-create"><img src="https://agentmods.dev/badge/skills/matteocervelli/llms/project-create.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.00058 | $0.01089 |
| Opus 5.5 | $0.00023 | $0.00436 |
| Sonnet 5.5 | $0.00012 | $0.00218 |
| Haiku 4.5 | $0.00006 | $0.00109 |
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 1mo 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Create Skill
Purpose
Initialize new projects with complete setup, documentation structure, quality tools, and CI/CD pipeline.
Usage
/project-create <project-name>
Repository Setup
# Create project structure
mkdir -p <project-name>/{docs/{architecture,guides,implementation,PRD},src,tests,.github/workflows}
cd <project-name>
# Initialize Git and GitHub
git init
gh repo create <project-name> --private --description="[Project description]"
git remote add origin https://github.com/$(gh api user --jq .login)/<project-name>.git
Core Documentation
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
.env
.env.local
# Dependencies
node_modules/
__pycache__/
# Build outputs
dist/
build/
*.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.
- 1mo ago First seen · 167 lines · 58 tokens per session scan A a852dc89adab
project-create is a skill published in the GitHub repository matteocervelli/llms (25 stars, last pushed 5mo ago), licensed MIT. It adds 58 tokens to every session and 1,089 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
nx-workspace-patterns
Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.
bazel-build-optimization
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.
babysit
Use when a user asks to babysit, monitor, keep checking, keep an eye on, or report when a pull request, CI run, ticket, deployment, or other changing target reaches an outcome.
add-azuredevops
Adds Azure DevOps connector to a Power Apps code app. Use when querying work items, creating bugs, managing pipelines, or making ADO API calls.
atmos-modernization
Atmos Modernization: migrate deprecated or legacy Atmos patterns to current names, Native CI, Atmos Pro drift detection, dependencies.components, nametemplate, and declared secrets.
factory
Experimental workflow for configuring an autonomous software delivery factory. Use when choosing feedback sources, schedules, worktree behavior, autonomy gates, or host automations.