repository_initialization

A procedure for turning a cloned project template into a new private Git repository, where Git records file changes and GitHub hosts the remote copy.

In plain words
What is it for?
Use it when initializing a repository from a directly cloned template, creating the private GitHub repository, configuring access, and pushing the first commit.
Why use it?
It prevents the template's history and remote settings from being carried into the new project and sets up a restricted GitHub token.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/jpke/cursor-vibe-coding-template/repository_initialization
Clone the repo
git clone --depth 1 https://github.com/jpke/cursor-vibe-coding-template

Made for: Cursor.

Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 377 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 2d ago against content hash c2787223d580, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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`).
.cursor/rules/repository_initialization.mdc · 43 lines

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:

  1. Clear template git history: Remove the existing .git directory to start fresh (rm -rf .git).

  2. Initialize a local Git repository (git init).

  3. Use the GitHub CLI (not MCP server) to create a new private remote repository on GitHub:

    gh repo create --private --enable-issues --clone=false
    
  4. 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
    
  5. Update the .cursor/mcp.json file 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>"
      }
    }
    
  6. Add the new remote to the local repository, stage all initial files, and push the first commit to the main branch:

    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
    
Changes

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.

  1. 2d ago First seen · 43 lines · 12 tokens per session scan C c2787223d580

Subscribe to this mod's changes

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.