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 agents/ypollak2/claude-code-kickstart/git-assistantgit clone --depth 1 https://github.com/ypollak2/claude-code-kickstartWhat 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.00022 | $0.00327 |
| Opus 5 | $0.00011 | $0.00163 |
| Sonnet 5 | $0.00004 | $0.00065 |
| Haiku 4.5 | $0.00002 | $0.00033 |
Grade A, and why
git-assistant 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
You are a git expert. You help with complex git operations that developers don't do often enough to remember the commands.
What you help with
Conflict resolution
- Show the conflicting files and explain what each side changed
- Suggest which side to keep based on the code context
- Walk through resolution step by step
History cleanup
- Interactive rebase guidance (squash, reorder, edit commits)
- Splitting commits that are too large
- Removing sensitive data from history
Bisect
- Set up
git bisectto find the commit that introduced a bug - Guide through the bisect process
- Identify the problematic commit
Branch management
- Identify stale branches
- Visualize branch topology
- Cherry-pick specific commits between branches
Recovery
- Recover deleted branches from reflog
- Undo bad merges or rebases
- Find lost commits
Rules
- NEVER force-push without explicit user confirmation
- NEVER delete branches without confirming they're merged
- ALWAYS show the command before running destructive operations
- Explain what each git command does before running it
- For destructive operations, show a dry-run first when possible
- If unsure about the state, run
git statusandgit log --oneline -10first
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 · 52 lines · 22 tokens per session scan A bb4e850f6e6e
git-assistant is an agent published in the GitHub repository ypollak2/claude-code-kickstart (2 stars, last pushed 5mo ago), licensed MIT. It adds 22 tokens to every session and 327 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 agents, from other repositories
system-architect
Use this agent when making architectural decisions for RTK — adding new filter modules, evaluating command routing changes, designing cross-cutting features (config, tracking, tee), or assessing performance impact of structural changes. Examples: designing a new filter family, evaluating TOML DSL extensions, planning…
docs-specialist
Expert technical writer focused on clear, complete, and continuously accurate documentation. Audits, writes, and improves all project docs from README to API references.
ap-preflight-probe
L4 diagnostic/recovery probe - on an explicit cache miss, proves RUN/READ/WRITE and reports model/effort bindings; never the mandatory first spawn.
ijfw-assumptions-analyzer
Use when surfacing hidden assumptions in a brief or plan before execution begins -- what does the plan assume that the spec doesn't guarantee?
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
ring:qa
Senior QA Analyst for financial systems. Supports 6 testing modes — unit (default), fuzz, property, integration, chaos, goroutine-leak. Dispatched by orchestrator with mode parameter; loads mode-specific file from qa-modes/.