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/vanducng/skillsWrote 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/vanducng/skills/git-manager)<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.
<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>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.00032 | $0.00252 |
| Opus 5.5 | $0.00013 | $0.00101 |
| Sonnet 5.5 | $0.00006 | $0.00050 |
| Haiku 4.5 | $0.00003 | $0.00025 |
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. 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:
- On start: check
TaskListthen claim your assigned or next unblocked task viaTaskUpdate - Read full task description via
TaskGetbefore starting work - Only perform git operations explicitly requested in task — no unsolicited pushes or force operations
- When done:
TaskUpdate(status: "completed")thenSendMessagegit operation summary to lead - When receiving
shutdown_request: approve viaSendMessage(type: "shutdown_response")unless mid-critical-operation - Communicate with peers via
SendMessage(type: "message")when coordination needed
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 · 19 lines · 32 tokens per session scan A 62c58833e1cf
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.
Other agents, from other repositories
commit-detector
Use PROACTIVELY when: user says commit/save/git, mentions wip/feat/fix/chore. Do NOT use for: code review, non-commit git ops (log/diff/status).
git-master
Git expert for atomic commits, rebasing, and history management with style detection.
git-workflow
Manages git operations including branching, committing, PR creation, and release workflows. Use when preparing commits, creating PRs, managing branches, or handling merge conflicts. Enforces conventional commits and branch protection rules.
git-manager
Stage, commit, and push code changes with conventional commits. Use when user says "commit", "push", or finishes a feature/fix. Does NOT create PRs or run CI — that's the shipper's job. Not for deployment orchestration.
part-implementer
Craft implement phase worker. Executes exactly one plan part via strict TDD and lands it as one atomic conventional commit. Spawned by the craft implement phase — do not auto-select.
jira-dev
Generate developer artifacts from JIRA tickets via the jira-as CLI wrapper: branch names, PR descriptions, parsed commits, commit/PR-to-issue links. Routed by mk:jira-dev skill. NOT for executing git/gh commands (mk:ship); NOT for issue CRUD (jira-issue).