git-manager

git-manager is an agent for Claude Code from vanducng/skills. It costs 32 tokens per session (252 once invoked), scanned A, original, MIT.

An agent for handling Git version-control operations such as staging changes, creating commits, and pushing them to a remote repository. It uses conventional commit messages, a shared format for describing changes.

In plain words
What is it for?
Use it after a feature or fix is finished to stage files, make a correctly formatted commit, and push it when explicitly requested.
Why use it?
It removes the manual steps involved in packaging completed code changes and sending them to the team repository. It is intended for requests to commit or push work.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter.

Part of the vd plugin — 91 skills, 14 agents shipped together

Good fit Use it after a feature or fix is finished to stage files, make a correctly formatted commit, and push it when explicitly requested.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/vanducng/skills/git-manager
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.

Clone the repo
git clone --depth 1 https://github.com/vanducng/skills

Made for: Claude Code.

Or install vd, the plugin that ships this one along with the rest of its 91 skills, 14 agents.

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

agentmods badge for git-manager

README.md
[![agentmods](https://agentmods.dev/badge/agents/vanducng/skills/git-manager/github.svg)](https://agentmods.dev/agents/vanducng/skills/git-manager)
Your own site
<a href="https://agentmods.dev/agents/vanducng/skills/git-manager"><img src="https://agentmods.dev/badge/agents/vanducng/skills/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.

agentmods 80×15 button for git-manager

Your own site · 80×15
<a href="https://agentmods.dev/agents/vanducng/skills/git-manager"><img src="https://agentmods.dev/badge/agents/vanducng/skills/git-manager.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 32 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 252 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00032 $0.00252
Opus 5.5 $0.00013 $0.00101
Sonnet 5.5 $0.00006 $0.00050
Haiku 4.5 $0.00003 $0.00025

Measured 1mo ago against content hash 62c58833e1cf, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 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.

agents/git-manager.md · 19 lines

What it actually says

You are a Git Operations Specialist. Execute workflow in EXACTLY 2-4 tool calls. No exploration phase. Activate git skill. IMPORTANT: Ensure token efficiency while maintaining high quality.

Team Mode (when spawned as teammate)

When operating as a team member:

  1. On start: check TaskList then claim your assigned or next unblocked task via TaskUpdate
  2. Read full task description via TaskGet before starting work
  3. Only perform git operations explicitly requested in task — no unsolicited pushes or force operations
  4. When done: TaskUpdate(status: "completed") then SendMessage git operation summary to lead
  5. When receiving shutdown_request: approve via SendMessage(type: "shutdown_response") unless mid-critical-operation
  6. Communicate with peers via SendMessage(type: "message") when coordination needed
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. 1mo ago First seen · 19 lines · 32 tokens per session scan A 62c58833e1cf

Subscribe to this mod's changes

git-manager is an agent published in the GitHub repository vanducng/skills (8 stars, last pushed today), licensed MIT. It adds 32 tokens to every session and 252 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-31.