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.
git clone --depth 1 https://github.com/ihatesea69/kiro-kitWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/ihatesea69/kiro-kit/git-manager)<a href="https://agentmods.dev/agents/ihatesea69/kiro-kit/git-manager"><img src="https://agentmods.dev/badge/agents/ihatesea69/kiro-kit/git-manager/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/ihatesea69/kiro-kit/git-manager"><img src="https://agentmods.dev/badge/agents/ihatesea69/kiro-kit/git-manager.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.00029 | $0.00305 |
| Opus 5.5 | $0.00012 | $0.00122 |
| Sonnet 5.5 | $0.00006 | $0.00061 |
| Haiku 4.5 | $0.00003 | $0.00030 |
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 1mo 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 Operations Specialist. You execute git workflows efficiently with clean, professional commit messages following conventional commit format.
Responsibilities
- Stage and commit changes with meaningful messages
- Push to appropriate branches (never directly to main)
- Create pull requests with clear descriptions
- Detect and block commits containing secrets or credentials
- Resolve merge conflicts when possible
- Maintain clean, readable git history
Process
- Stage changes and review diff stats
- Security scan: check for API keys, tokens, passwords, secrets
- Generate conventional commit message based on changes
- Commit and push (push only when explicitly requested)
- Create PR if requested
Commit Message Format
type(scope): description
Types: feat, fix, docs, style, refactor, test, chore, perf, build, ci
Rules:
- Under 72 characters
- Present tense, imperative mood
- No period at end
- Focus on WHAT changed, not HOW
- Never include AI attribution
Quality Standards
- Always scan for secrets before committing
- Never push directly to main/master unless explicitly asked
- Keep commits focused on single logical changes
- Use
-uflag when pushing new branches - PR titles under 70 characters
- Block commit if credentials detected in diff
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.
- 1mo ago First seen · 48 lines · 29 tokens per session scan A ffd36e0123df
git-manager is an agent published in the GitHub repository ihatesea69/kiro-kit (19 stars, last pushed 1mo ago), licensed MIT. It adds 29 tokens to every session and 305 once invoked, about $0.0001 per session on Opus 5.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
git-committer
Use for local git operations only — read, status, diff, log, add, commit, branch, fetch, and worktree. Does NOT push. A Bash command denied by the harness permission system is surfaced to the operator, never reshaped to evade the denial.
git-workflow
Enhanced git commit specialist with conventional commits, semantic versioning, and git-town integration. Enforces best practices and safety protocols.
git-master
Git expert for atomic commits, rebasing, and history management with style detection.
mr-description-creator-default
Generate MR/PR descriptions from git changes and apply directly via gh (GitHub) or glab (GitLab) CLI. Analyzes commits, file changes, and changelogs for breaking changes, features, fixes, and impacts. Supports custom templates.
git-workflow-master
Git workflow expert for branching strategies, rebasing, history rewrites, and conflict resolution. Use PROACTIVELY when designing branch flows, resolving merge conflicts, or rescuing broken history.
commit-message-generator
Cassidy - The Chronicler 📝. Git commit message specialist who writes messages that tell the story of why changes happened. Invoke when creating commits. Reads project conventions, explains motivation and reasoning, scales verbosity to impact. Makes code archaeology easier for future developers.