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 rules/jpke/cursor-vibe-coding-template/repository_initializationgit clone --depth 1 https://github.com/jpke/cursor-vibe-coding-templateWhat 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.00012 | $0.00377 |
| Opus 5 | $0.00006 | $0.00188 |
| Sonnet 5 | $0.00002 | $0.00075 |
| Haiku 4.5 | $0.00001 | $0.00038 |
Grade C, and why
repository_initialization 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 2d 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.
1. **Clear template git history**: Remove the existing `.git` directory to start fresh (`rm -rf .git`). What it actually says
Repository Initialization
Note: This is only needed when cloning the template directly. When using this as a GitHub template (recommended), a fresh repository is automatically created.
When you request to "initialize git repo" (only needed for cloned templates), I will perform the following steps:
-
Clear template git history: Remove the existing
.gitdirectory to start fresh (rm -rf .git). -
Initialize a local Git repository (
git init). -
Use the GitHub CLI (not MCP server) to create a new private remote repository on GitHub:
gh repo create --private --enable-issues --clone=false -
Create a repository-scoped GitHub Personal Access Token using the GitHub CLI:
gh auth token --hostname github.com --scopes "issues:write,contents:read,metadata:read" --repo-specific -
Update the
.cursor/mcp.jsonfile to use the new scoped GitHub PAT in the GitHub MCP server configuration:"github": { "url": "https://api.githubcopilot.com/mcp/", "headers": { "Authorization": "Bearer <new_scoped_pat>" } } -
Add the new remote to the local repository, stage all initial files, and push the first commit to the
mainbranch:git remote add origin [email protected]:username/repo-name.git # Use SSH format for authentication git add . git commit -m "feat: initial project setup" git push -u origin main
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.
- 2d ago First seen · 43 lines · 12 tokens per session scan C c2787223d580
repository_initialization is a cursor rule published in the GitHub repository jpke/cursor-vibe-coding-template (16 stars, last pushed 1y ago), licensed MIT. It adds 12 tokens to every session and 377 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other cursor rules, from other repositories
90-devops-deployment
Docker, CI/CD, AWS, Vercel, and VPS deployment rules.
00-global-architect
Global default behavior for the entire repository.
55-data-model-versioning
Dataset versioning, model checkpoint management, and training reproducibility rules.
85-error-observability
Error handling, logging, and observability rules.
30-database-postgres
PostgreSQL and persistence rules.
35-api-contracts
API versioning, contracts, and schema evolution rules.