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 skills/selfagency/beans-mcp/git-mcp-workflownpx skills add selfagency/beans-mcp --skill git-mcp-workflowgit clone --depth 1 https://github.com/selfagency/beans-mcpWrote 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/skills/selfagency/beans-mcp/git-mcp-workflow)<a href="https://agentmods.dev/skills/selfagency/beans-mcp/git-mcp-workflow"><img src="https://agentmods.dev/badge/skills/selfagency/beans-mcp/git-mcp-workflow.svg" alt="Measured on agentmods" 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 | $0.00160 | $0.02683 |
| Opus 5 | $0.00080 | $0.01341 |
| Sonnet 5 | $0.00032 | $0.00537 |
| Haiku 4.5 | $0.00016 | $0.00268 |
Grade A, and why
git-mcp-workflow 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 4d 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 — 219 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git MCP Workflow
An MCP-first workflow skill for repositories exposed through git-mcp.
This skill adapts common Git guidance for a world where the preferred interface is the server's tool catalog, not ad-hoc shell commands. It covers both everyday Git work and the spicier recovery and history-editing cases.
Why LLMs Must Not Use the Git CLI
Using git directly via the shell is highly error-prone for LLMs and should be considered forbidden except as a narrow last resort.
The root cause is structural: Git commands frequently require commit messages, branch names, file paths, and other string arguments that contain spaces, quotes, special characters, or newlines. Shell interpreters handle quoting through multiple layers (single quotes, double quotes, $'...' escapes, heredocs) and the rules differ between sh, bash, and zsh. LLMs routinely produce subtly malformed quoting that causes:
- Commit messages truncated at the first space or quote character
- Arguments interpreted as flags (a message starting with
-becomes a flag) - Multi-line messages collapsed to one line or silently dropped
- Shell word-splitting breaking file paths that contain spaces
- Quote nesting errors causing the command to hang waiting for a closing delimiter
$or backtick characters in messages accidentally triggering command substitution
These errors are often silent: the command appears to succeed, but the result is wrong (e.g., a commit message of "fix" instead of "fix: resolve null pointer in auth handler"). LLMs typically cannot observe the actual error because the shell may not surface it clearly in the tool output.
The git-mcp server solves all of this. Every tool parameter is a typed, validated field that the server passes directly to simple-git as an argument array, bypassing shell interpretation entirely. There are no quoting problems, no interpolation hazards, and no silent truncation.
Rule: Always use git-mcp MCP tools for git operations. Never invoke git via shell unless the specific operation is genuinely not available through any git-mcp tool.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 219 lines · 160 tokens per session scan A b46af2d2ba0f
git-mcp-workflow is a skill published in the GitHub repository selfagency/beans-mcp (0 stars, last pushed 4mo ago), licensed MIT. It adds 160 tokens to every session and 2,683 once invoked, about $0.0008 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-31.
Other skills, from other repositories
issue-triage
Issue triage: audit open issues, categorize, detect duplicates, cross-ref PRs, risk assessment, post comments. Args: "all" for deep analysis of all, issue numbers to focus (e.g. "42 57"), "en"/"fr" for language, no arg = audit only in French.
rtk-triage
Triage complet RTK : exécute issue-triage + pr-triage en parallèle, puis croise les données pour détecter doubles couvertures, trous sécurité, P0 sans PR, et conflits internes. Sauvegarde dans claudedocs/RTK-YYYY-MM-DD.md. Args: "en"/"fr" pour la langue (défaut: fr), "save" pour forcer la sauvegarde.
task-planning
Turn a Paperclip issue or request into a structured implementation plan with child task graph, blockers, owners, and acceptance criteria, then save it as the issue plan document.
github-operations
GitHub CLI operations for issues, PRs, milestones, and Projects v2. Covers gh commands, REST API patterns, and automation scripts. Use when managing GitHub issues, PRs, milestones, or Projects with gh.
issue-progress-tracking
GitHub issue workflow ceremony using gh CLI — labels issues as in-progress, creates feature branches (issue/N-description), commits with issue references, posts progress comments, and links PRs with Closes #N. Keeps issues in sync with development work. Use when starting work on an issue, tracking progress, or…
epiq
Workflow rules for working the epiq issue board — use the epiq MCP, sync on demand, scope tickets small, keep status/tags accurate, and communicate via comments.