Spec Kit is an open-source toolkit for defining software requirements and plans before implementation with an AI coding agent. It is used by developers and organizations following a spec-driven development process.
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.
git clone --depth 1 https://github.com/github/spec-kitWrote 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/commands/github/spec-kit/speckit.git.initialize)<a href="https://agentmods.dev/commands/github/spec-kit/speckit.git.initialize"><img src="https://agentmods.dev/badge/commands/github/spec-kit/speckit.git.initialize/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/commands/github/spec-kit/speckit.git.initialize"><img src="https://agentmods.dev/badge/commands/github/spec-kit/speckit.git.initialize.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.00008 | $0.00353 |
| Opus 5.5 | $0.00003 | $0.00141 |
| Sonnet 5.5 | $0.00002 | $0.00071 |
| Haiku 4.5 | $0.00001 | $0.00035 |
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 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.
Copies of this mod
8 near-identical copies found in the catalogue:
- speckit.git.initialize — 100% identical, 0 lines differ
- speckit.git.initialize — 100% identical, 48 lines differ
- speckit.git.initialize — 100% identical, 0 lines differ
- speckit.git.initialize — 100% identical, 0 lines differ
- speckit.git.initialize — 100% identical, 0 lines differ
- speckit.git.initialize — 98% identical, 2 lines differ
- speckit.git.initialize — 98% identical, 48 lines differ
- speckit.git.initialize — 98% identical, 2 lines differ
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:
[OK] 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.
- 1mo ago First seen · 50 lines · 8 tokens per session scan A d89e32ec18b3
speckit.git.initialize is a command published in the GitHub repository github/spec-kit (141,437 stars, last pushed today), licensed MIT. It adds 8 tokens to every session and 353 once invoked, about $0.0000 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-08-30.
Other commands, from other repositories
octo-retro
Your first output line MUST be: 🐙 Octopus Retrospective.
apex-git-commit
Stage everything except agent-output/, infra/, and .github/skills/sensei/ (unless on feat/skills-sensei), auto-generate a conventional commit, push, then prompt to open or update a PR. CLI-only (git + gh).
dev
Developer tools — debug, commit, PR, code review, refactoring.
explain
/explain Explain the last agent action (quick mode) /explain --verbose Full trace with file changes and decision rationale /explain --story STORY-XXX All actions for a story in chronological order /explain --agent Last action by a specific agent /explain --session All actions from a specific session /explain --diff…
undo
You are the Undo Manager. You identify, preview, and safely revert recent agent actions using git-based rollback. You never undo blindly -- you always show what will change, verify reversibility, and confirm no regressions are introduced afterward.
quick
Role: Minimal-ceremony feature workflow for solo developers and small changes. Implement → test → commit. No PRD required, no full pipeline overhead.