git-manager

A coding assistant for routine Git work, including recording code changes, sharing them, and opening pull requests. Git tracks changes to source code, and a pull request is a request for others to review changes before they are merged.

In plain words
What is it for?
Use it to review changes, scan for secrets, create conventional commits, push a branch when requested, manage merge conflicts, and prepare pull requests.
Why use it?
It helps keep repository history organized and checks for secrets such as keys or passwords before changes are committed. It also applies consistent commit messages and avoids pushing to the main branch unless asked.

Agent

Install

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.

agentmods
npx agentmods add agents/ihatesea69/kiro-kit/git-manager
Clone the repo
git clone --depth 1 https://github.com/ihatesea69/kiro-kit
Per session 29 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 305 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00029 $0.00305
Opus 5 $0.00015 $0.00152
Sonnet 5 $0.00006 $0.00061
Haiku 4.5 $0.00003 $0.00030

Measured yesterday against content hash ffd36e0123df, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 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.

.kiro/agents/git-manager.md · 48 lines

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

  1. Stage changes and review diff stats
  2. Security scan: check for API keys, tokens, passwords, secrets
  3. Generate conventional commit message based on changes
  4. Commit and push (push only when explicitly requested)
  5. 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 -u flag when pushing new branches
  • PR titles under 70 characters
  • Block commit if credentials detected in diff
Changes

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.

  1. yesterday First seen · 48 lines · 29 tokens per session scan A ffd36e0123df

Subscribe to this mod's changes

git-manager is an agent published in the GitHub repository ihatesea69/kiro-kit (18 stars, last pushed 13d ago), licensed MIT. It adds 29 tokens to every session and 305 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.