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/butgo/butgo-specdrive-lab/git-commitnpx skills add butgo/butgo-specdrive-lab --skill git-commitgit clone --depth 1 https://github.com/butgo/butgo-specdrive-labWhat 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.00025 | $0.00321 |
| Opus 5 | $0.00013 | $0.00161 |
| Sonnet 5 | $0.00005 | $0.00064 |
| Haiku 4.5 | $0.00003 | $0.00032 |
Grade A, and why
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 yesterday.
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.
What it actually says
Git Commit
Use the simplest flow.
Preferred argument-based invocation:
$git commit
Rule
- Excluded files are controlled only by
.gitignore. - Stage with
git add .. - Generate the commit message from
docs/projects/standards/git-policy.md. - Commit with the approved message.
- Before push, check whether the current branch exists on
origin. - If the remote branch exists, push with
git push. - If the remote branch does not exist, report that and use
git push -u origin <current-branch>only after approval.
Flow
- Check current branch.
- Check
git status --short. - Propose one commit message.
- After approval, run:
git add .
git commit -m "<message>"
- Before push, check remote branch existence:
git ls-remote --heads origin <current-branch>
- If the branch exists on
origin, run:
git push
- If the branch does not exist on
origin, ask approval for the upstream push, then run:
git push -u origin <current-branch>
Output
Keep output minimal:
- branch
- remote branch existence before push
- proposed commit message
- approval prompt
- final result
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday First seen · 65 lines · 25 tokens per session scan A 2bdd160d3baf
git-commit is a skill published in the GitHub repository butgo/butgo-specdrive-lab (1 stars, last pushed 3mo ago), licensed MIT. It adds 25 tokens to every session and 321 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
codex-auth-setup
Install or refresh codex-multi-auth for the official Codex CLI, run first login, and verify account health and routing.
codexu-release
Run this skill from the repository root. Treat the release as a real public publish: verify the current remote state first, keep unrelated user changes out of release commits, and report exactly what was built, pushed, and released.
example
Example fixture skill for scanner regression coverage.
codexu-pr-review
Review codexU pull requests and decide whether they should be merged, changed, split, declined, or kept as a fork based on product positioning, roadmap, privacy, data semantics, native macOS design, architecture, scope, and verification. Use for PR review, mergeability assessment, contribution triage, and feature-fit…
agentflow
AgentFlow workflow skill. Use this skill when the user needs Orchestrate autonomous AI development pipelines through your Kanban board (Asana, GitHub Projects, Linear). Manages multi-worker Claude Code dispatch, deterministic quality gates, adversarial review, per-task cost tracking, and crash-proof pipeline execution…
context-canvas-reflection
Run one bounded trajectory reflection when repeated same-cause failures, contradicted assumptions, real-use failure after local green, material scope drift, a materially unresolved phase boundary, an unapproved authority-sensitive next effect, or user doubt suggests the current path may be wrong. Use Context Canvas…