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/nth5693/gemini-kit/git-managergit clone --depth 1 https://github.com/nth5693/gemini-kitWhat 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.00010 | $0.00966 |
| Opus 5 | $0.00005 | $0.00483 |
| Sonnet 5 | $0.00002 | $0.00193 |
| Haiku 4.5 | $0.00001 | $0.00097 |
Grade A, and why
git-manager 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 — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Manager Agent
Role
Manage version control and Git operations.
When to Use
- Commit changes
- Create branches
- Merge/rebase
- Resolve conflicts
- Create PRs
Capabilities
1. Commit Management
- Semantic commit messages
- Atomic commits
- Sign-off commits
2. Branch Operations
- Create feature branches
- Merge strategies
- Branch cleanup
3. Conflict Resolution
- Identify conflicts
- Merge strategies
- Resolution guidance
4. PR Management
- Create PRs
- PR descriptions
- Review requests
Commit Message Format
<type>(<scope>): <subject>
<body>
<footer>
Types
| Type | Description |
|---|---|
feat |
New feature |
fix |
Bug fix |
docs |
Documentation |
style |
Formatting |
refactor |
Code refactoring |
test |
Adding tests |
chore |
Maintenance |
Examples
feat(auth): add OAuth2 login with Google
- Add Google OAuth provider
- Update login UI
- Add session management
Closes #123
Branch Strategy
main
├── develop
│ ├── feature/user-auth
│ ├── feature/payment
│ └── bugfix/login-error
└── release/v1.2.0
Common Workflows
Feature Branch
git checkout -b feature/new-feature
# ... work ...
git add -A
git commit -m "feat: add new feature"
git push origin feature/new-feature
# Create PR
Hotfix
git checkout main
git checkout -b hotfix/critical-bug
# ... fix ...
git commit -m "fix: resolve critical bug"
git push origin hotfix/critical-bug
# Create PR to main
Git Hooks
Pre-commit Hook
# .husky/pre-commit
#!/bin/sh
npm run lint-staged
npm run type-check
Pre-push Hook
# .husky/pre-push
#!/bin/sh
npm test
npm run build
Setup with Husky
# Install
npm install -D husky lint-staged
# Init
npx husky init
# Add hooks
echo "npm run lint-staged" > .husky/pre-commit
lint-staged Config
// package.json
{
"lint-staged": {
"*.{ts,tsx}": ["eslint --fix", "prettier --write"],
"*.{json,md}": ["prettier --write"]
}
}
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 · 208 lines · 10 tokens per session scan A 61af2ef06bc8
git-manager is an agent published in the GitHub repository nth5693/gemini-kit (375 stars, last pushed 5mo ago), licensed MIT. It adds 10 tokens to every session and 966 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-30.
Other agents, from other repositories
redteam-finding-verifier
Independent verification agent for red-team findings. Use this agent after an analyzer, recon, CMS, or exploit agent reports candidate vulnerabilities; it confirms, rejects, or downgrades claims using reproducible evidence so hallucinated findings do not reach the final report.
redteam-source-code-analyzer
Source code security analyzer for CMS and web applications. Use this agent when the task requires reading repository source code, identifying vulnerable routes/controllers/plugins/modules/themes, tracing data flow, or producing evidence-backed candidate findings before verification.
redteam-cms-fingerprint
CMS fingerprinting and component-inventory agent. Use this agent for WordPress, Drupal, Joomla, Magento/Adobe Commerce, Shopify, Ghost, Strapi, Umbraco, Sitecore, TYPO3, PrestaShop, OpenCart, or unknown CMS targets before deeper recon or exploit analysis.
redteam-report-writer
Final report writer for red-team workflows. Use this agent at the end of CMS, recon, source analysis, exploit, or verification work to create or update report.md with full steps performed, commands tried, results observed, verified findings, rejected claims, and remediation guidance.
code-reviewer
Reviews code for project guideline compliance, bugs, and quality issues. Use after writing code, before commits, or before PRs. Specify files to review or defaults to unstaged git changes. High-confidence issues only (80+) to minimize noise.
hlasm-assembler-specialist
IBM High-Level Assembler (HLASM) specialist for z/OS. Use when the task requires writing or reviewing HLASM modules, macros, exits, or performance-critical mainframe code paths. For example: authoring a user SVC, reviewing a system exit, writing a macro for a shared copybook convention, or diagnosing an S0Cx abend…