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 skills/racecraft-lab/paddock/speckit-git-initializenpx skills add racecraft-lab/Paddock --skill speckit-git-initializegit clone --depth 1 https://github.com/racecraft-lab/PaddockWhat 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.00016 | $0.00398 |
| Opus 5 | $0.00008 | $0.00199 |
| Sonnet 5 | $0.00003 | $0.00080 |
| Haiku 4.5 | $0.00002 | $0.00040 |
Grade A, and why
speckit-git-initialize 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 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.
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.
This is a copy
100% identical to speckit-git-initialize — 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.
What it actually says
Initialize Git Repository
Initialize a Git repository in the current project directory if one does not already exist.
Execution
Run the appropriate script from the project root:
- Bash:
.specify/extensions/git/scripts/bash/initialize-repo.sh - PowerShell:
.specify/extensions/git/scripts/powershell/initialize-repo.ps1
If the extension scripts are not found, fall back to:
- Bash:
git init && git add . && git commit -m "Initial commit from Specify template" - PowerShell:
git init; git add .; git commit -m "Initial commit from Specify template"
The script handles all checks internally:
- Skips if Git is not available
- Skips if already inside a Git repository
- Runs
git init,git add ., andgit commitwith an initial commit message
Customization
Replace the script to add project-specific Git initialization steps:
- Custom
.gitignoretemplates - Default branch naming (
git config init.defaultBranch) - Git LFS setup
- Git hooks installation
- Commit signing configuration
- Git Flow initialization
Output
On success:
✓ Git repository initialized
Graceful Degradation
If Git is not installed:
- Warn the user
- Skip repository initialization
- The project continues to function without Git (specs can still be created under
specs/)
If Git is installed but git init, git add ., or git commit fails:
- Surface the error to the user
- Stop this command rather than continuing with a partially initialized repository
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 · 54 lines · 16 tokens per session scan A 2c3e80ca3f59
speckit-git-initialize is a skill published in the GitHub repository racecraft-lab/Paddock (11 stars, last pushed 2mo ago), licensed MIT. It adds 16 tokens to every session and 398 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to speckit-git-initialize, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
mission-control
Interact with Mission Control — AI agent orchestration dashboard. Use when registering agents, managing tasks, syncing skills, or querying agent/task status via MC APIs.
unleash
Run as a named worker draining the task queue in my private coordination repo, where each task is a GitHub Issue — claim one task at a time, check blocked-by dependencies, plan with explicit assumptions, execute, validate against acceptance criteria, and record results as comments; then stay in ambush behind a…
status
Read-only console of a kraken queue — everything the operator reads in one place. Runs kraken.py status, which computes the review queue (awaiting-merge, with PR links), the decision queue (needs-decision), what is still in flight (every live claim ref — worker name + lease age, flagging expired leases), a…
init
Stand up a kraken coordination repo end to end — verify or create the private repo, install the bundled task template, remove everything an earlier release installed to be executed server-side, and create the canonical labels. Strictly setup, the write-side twin of status's read-only console; it reads and writes no…
nextjs-app-router-dev
Next.js App Router 开发与排障：Edge middleware、SQLite、session 认证。.
refactor
Surgical code refactoring to improve maintainability without changing behavior. Covers extracting functions, renaming variables, breaking down god functions, improving type safety, eliminating code smells, and applying design patterns. Less drastic than repo-rebuilder; use for gradual improvements.