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/brain-bootstrap/claude-code-brain-bootstrap/gitnpx skills add brain-bootstrap/claude-code-brain-bootstrap --skill gitgit clone --depth 1 https://github.com/brain-bootstrap/claude-code-brain-bootstrapWhat 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.00034 | $0.00537 |
| Opus 5 | $0.00017 | $0.00269 |
| Sonnet 5 | $0.00007 | $0.00107 |
| Haiku 4.5 | $0.00003 | $0.00054 |
Grade A, and why
git 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.
What it actually says
Git Skill
Git workflow helpers for everyday operations.
Usage
/git status # Current branch + dirty files + recent commits
/git branch # List branches
/git rebase main # Rebase onto main
/git commit <msg> # Stage all + commit
/git amend # Stage all + amend last commit
/git log # Last 20 commits
/git stash # Stash changes
/git stash pop # Pop stash
/git conflicts # Find conflict markers
⚠️ NEVER git push Autonomously
Always present the proposed command and wait for user confirmation:
Proposed: git push origin feature/my-branch
⏳ Waiting for your confirmation before pushing...
Instructions
Determine action from $ARGUMENTS:
| Argument | Action |
|---|---|
status |
git status --short + git --no-pager log --oneline -5 |
branch |
git branch --show-current |
branches |
git --no-pager branch -a | head -30 |
stash |
git stash |
stash pop |
git stash pop |
rebase main |
git fetch origin main && git rebase origin/main |
commit <message> |
git add -A && git commit -m "<message>" |
amend |
git add -A && git commit --amend --no-edit |
log |
git --no-pager log --oneline -20 |
conflicts |
grep -rn '^<<<<<<<|^=======|^>>>>>>>' . 2>/dev/null | head -20 |
Branch Naming Convention:
- Feature:
feat/<ticket-id>-<short-description> - Fix:
fix/<ticket-id>-<short-description> - Chore:
chore/<description>
Pre-Push Checklist (present to user before any push):
- ✅ Build passes
- ✅ Tests pass
- ✅ Lint clean on changed files
- ✅ No conflict markers in repo
- ✅ Diff review complete (merge-base aware)
- 📋 Proposed:
git push origin <branch> - ⏳ Waiting for user confirmation...
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 · 62 lines · 34 tokens per session scan A e96e64ca00c5
git is a skill published in the GitHub repository brain-bootstrap/claude-code-brain-bootstrap (11 stars, last pushed 4mo ago), licensed MIT. It adds 34 tokens to every session and 537 once invoked, about $0.0002 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-30.
Other skills, from other repositories
implement
TRIGGER when: user asks to implement, fix, build, or work on something — whether from a docs/wip plan OR a standalone task (bug fix, GitHub issue, one-off change). Examples: "work on task 1", "fix this bug", "implement feature X from the issue". Provides structured execution with profile detection, dependency…
review-spec
Use after implementing tasks or mid-feature to verify code matches design docs and ensure they are in sync. Detects spec deviations, missing implementations, doc inconsistencies, and outdated docs in design and implementation documentation.
chain-of-verification
Apply Chain-of-Verification (CoVe) prompting to improve response accuracy through self-verification. Use when complex questions require fact-checking, technical accuracy, or multi-step reasoning.
review-design
Review design, implementation, and task documents produced by design. Evaluates document quality, internal consistency, and technical soundness. Use after design completes and before starting implement.
review-code
Code review of current git changes with an expert senior-engineer lens. Detects SOLID violations, security risks, and proposes actionable improvements. Use when performing code reviews.
dependency-handling
TRIGGER when: adding or upgrading any dependency — library, SDK, framework, API, IaC API version (K8s/Terraform/Helm), CRD, or container image. Use BEFORE writing the call. Forces context7/capy lookup instead of guessing.