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/arrrrny/zuraffa/speckit-git-commitnpx skills add arrrrny/zuraffa --skill speckit-git-commitgit clone --depth 1 https://github.com/arrrrny/zuraffaWhat 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.00018 | $0.00904 |
| Opus 5 | $0.00009 | $0.00452 |
| Sonnet 5 | $0.00004 | $0.00181 |
| Haiku 4.5 | $0.00002 | $0.00090 |
Grade A, and why
speckit-git-commit 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.
How it starts
The opening of the file, as written. The whole thing — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auto-Commit Changes
Automatically stage and commit all changes after a Spec Kit command completes.
Behavior
This command is invoked as a hook after (or before) core commands. It:
- Determines the event name from the hook context (e.g., if invoked as an
after_specifyhook, the event isafter_specify; ifbefore_plan, the event isbefore_plan) - Checks
.specify/extensions/git/git-config.ymlfor theauto_commitsection - Looks up the specific event key to see if auto-commit is enabled
- Falls back to
auto_commit.defaultif no event-specific key exists - Determines the commit message based on
commit_style(see below) - If enabled and there are uncommitted changes, runs
git add .+git commit
Commit Message Styles
Controlled by the commit_style key in .specify/extensions/git/git-config.yml:
fixed(default): use the per-commandmessageif configured, otherwise a generic[Spec Kit] Auto-commit <phase> <command>message.conventional: inspect the actual changes (git diff/git status) since the last commit and generate a single-line Conventional Commit message (type(scope): subject, e.g.feat: add OAuth specificationordocs: update implementation plan) that accurately summarizes the change. Write this message to a temporary file and pass the file's path to the script (see Execution below). The configuredmessagevalues are ignored in this mode.
Execution
Determine the event name from the hook that triggered this command, then run the script:
- Bash:
.specify/extensions/git/scripts/bash/auto-commit.sh <event_name> [--message-file <path>] - PowerShell:
.specify/extensions/git/scripts/powershell/auto-commit.ps1 <event_name> [-MessageFile <path>]
Replace <event_name> with the actual hook event (e.g., after_specify, before_plan, after_implement). Only pass a generated message when commit_style: conventional is configured — first check .specify/extensions/git/git-config.yml for the value of commit_style:
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 · 68 lines · 18 tokens per session scan A 06d33253f127
speckit-git-commit is a skill published in the GitHub repository arrrrny/zuraffa (5 stars, last pushed 2d ago), licensed MIT. It adds 18 tokens to every session and 904 once invoked, about $0.0001 per session on Opus 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-31.
Other skills, from other repositories
delivery-workflow
Executa fluxo de entrega a partir de GitHub Issue — branch, implementação, validação, docs, commit e PR. Use quando o usuário fornecer issue, ticket.
common-git-collaboration
Enforce version control best practices for commits, branching, pull requests, and repository security. Use when writing commits, creating branches, merging, or opening pull requests.
setup-husky-dotnet
Use when configuring Git hooks in .NET projects before team commits occur, to enforce commit message standards and code formatting automatically.
terradart-ship-wave
Ship a TerraDart Wave release — curated factories, examples/docs debt, catalog counts, CHANGELOG, and agentverify. Use when landing multiple related google resources as one user-visible release.
terradart-add-curated-resource
Add or update a curated Google Cloud factory via terradart wrap (schema.json, optional MM YAML, wrapper override, lint, regenerate). Use when extending terradartgoogle with a new google resource.
terradart-add-beta-resource
Add a beta-only curated factory to terradartgooglebeta (filtered-fixture extraction, googlebeta override, wrap with provider pin). Use when a later provider pin introduces a new beta-only google type — the current pin's beta-only catalog is filled.