Borrowing it
Nothing to install: this file belongs to PIsberg/vibetags. 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/PIsberg/vibetags/main/.claude/skills/speckit-git-initialize/SKILL.mdgit clone --depth 1 https://github.com/PIsberg/vibetagsWrote 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/pisberg/vibetags/speckit-git-initialize)<a href="https://agentmods.dev/skills/pisberg/vibetags/speckit-git-initialize"><img src="https://agentmods.dev/badge/skills/pisberg/vibetags/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/skills/pisberg/vibetags/speckit-git-initialize"><img src="https://agentmods.dev/badge/skills/pisberg/vibetags/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.00016 | $0.00399 |
| Opus 5.5 | $0.00006 | $0.00160 |
| Sonnet 5.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 28d 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 — 1 line 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.
- 28d ago First seen · 55 lines · 16 tokens per session scan A c70271bf4267
speckit-git-initialize is a skill published in the GitHub repository PIsberg/vibetags (25 stars, last pushed yesterday), licensed MIT. It adds 16 tokens to every session and 399 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to speckit-git-initialize, differing in 1 line, and is treated as a copy.
Other skills, from other repositories
omh-commit-pr-authoring
This is an OMH commit-pr-authoring workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
git-flow
Use this skill when committing, branching, opening a pull request, resolving conflicts, or recovering from a git mistake in any repository. Triggers: user mentions "commit", "branch", "PR", "pull request", "merge", "rebase", "conflict", "stash", "cherry-pick", "revert", "bisect", "reflog", "force push".
git-commit
Generate conventional commit messages for Java projects. Use when user says "commit", "create commit", "commit changes", or after completing code changes that need to be committed.
core-workflow
Detailed development workflow patterns, checklists, and standards. Auto-loads for complex tasks, planning, debugging, or when explicit patterns are needed. Contains session protocols, git conventions, security checklists, review-based validation, and communication standards.
pre-commit-audit
Deliver a fast pre-commit safety scan: file size, anonymity (author / affiliation strings in tex/bib), hardcoded secrets, and invisible-Unicode carriers. Use when the user requests a fast pre-commit safety scan: file size, anonymity (author / affiliation strings in tex/bib), hardcoded secrets, and invisible-Unicode…
latex-diff
Compare two LaTeX files, project directories, or Git revisions and produce human-readable plus machine-readable severity-graded semantic changes. Use when determining what changed between manuscript versions or preparing a revision audit bundle. Not for proofreading one version; use $proofread.