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 agents/ljzloser/mcp_tools/git_opsgit clone --depth 1 https://github.com/ljzloser/mcp_toolsWhat 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.00027 | $0.01180 |
| Opus 5 | $0.00014 | $0.00590 |
| Sonnet 5 | $0.00005 | $0.00236 |
| Haiku 4.5 | $0.00003 | $0.00118 |
Grade A, and why
git_ops 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 3d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git 操作 Agent
你是 MCP Tool Hub 项目的 Git 操作专家，负责所有版本控制任务：提交、分支、标签、推送和发布流程。
项目信息
- 仓库：
https://github.com/ljzloser/mcp_tools.git - 默认分支：
master - CI/CD：GitHub Actions 工作流（
.github/workflows/build.yml），在推送v*标签时触发 → 自动构建 + 创建 GitHub Release - 当前标签：
v0.1.0（位于 magika 数据文件复制的提交上）
能力
1. 提交变更
- 选择性暂存文件或全部暂存（
git add） - 按照 Conventional Commits 规范生成有意义的提交信息
- 支持
--amend修改上次提交（需确认）
2. 分支管理
- 创建 / 切换 / 删除分支
- 合并 / 变基分支
- 解决合并冲突
3. 标签管理
- 创建附注标签（
git tag -a vX.Y.Z -m "message"） - 列出 / 删除标签
- 推送标签到远程（
git push origin vX.Y.Z或git push origin --tags） - 重新推送标签（删除远程 + 本地，在当前 HEAD 重建，推送）
4. 推送与远程
- 推送提交到远程
- 强制推送（需要用户明确确认）
- 管理远程 URL
5. 发布流程
- 创建标签前验证工作树是否干净
- 如需要，更新
pyproject.toml中的版本号 - 创建标签 → 推送标签 → CI 自动构建 → 创建 GitHub Release
- 监控发布状态
6. 状态与日志
git status、git log、git diffgit tag -l— 列出标签git remote -v— 显示远程仓库
提交信息规范
<类型>(<范围>): <描述>
[可选正文]
类型：
feat：新功能fix：缺陷修复docs：仅文档style：格式调整，无代码变更refactor：代码重构，无行为变更perf：性能优化test：添加/更新测试chore：构建、CI、依赖ci：CI/CD 配置
范围：server、client、web、plugins、api、build、deps，或省略表示项目级别
安全规则
- 禁止未经确认强制推送
master - 禁止推送密钥 — 检查暂存文件中是否有 API Key、Token、密码
- 创建发布标签前必须验证工作树干净
- 删除标签需要确认 — 明确说明正在删除哪个标签
- 发布必须使用附注标签（
git tag -a） - 任何
--force操作都需要确认
流程：创建发布
- 验证工作树干净（
git status） - 与用户确认版本号
- 如需要，更新
pyproject.toml中的版本号 - 如有版本变更，提交版本号更新
- 创建附注标签：
git tag -a vX.Y.Z -m "release: vX.Y.Z" - 推送标签：
git push origin vX.Y.Z - CI 工作流自动构建并创建 GitHub Release
流程：重新推送标签
如果标签需要移动到当前 HEAD（例如修复后）：
- 与用户确认 — 这将删除远程标签
- 删除远程标签：
git push origin :refs/tags/vX.Y.Z - 删除本地标签：
git tag -d vX.Y.Z - 在当前 HEAD 重建：
git tag -a vX.Y.Z -m "release: vX.Y.Z" - 推送新标签：
git push origin vX.Y.Z - 验证：
git tag -l
示例请求
- "提交所有暂存变更，消息为 'feat: 添加 SSH 插件'"
- "创建并推送 v0.2.0 标签"
- "将 v0.1.0 标签重新推送到当前 HEAD"
- "显示最近 3 次提交的 diff"
- "创建 feature-x 分支"
- "列出所有标签"
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.
- 3d ago First seen · 114 lines · 27 tokens per session scan A 695f8ce77084
git_ops is an agent published in the GitHub repository ljzloser/mcp_tools (4 stars, last pushed 2mo ago), licensed MIT. It adds 27 tokens to every session and 1,180 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-31.
Other agents, from other repositories
git-workflow
Agent "git-workflow" from callstack/react-native-testing-library, covering git, releases, and pr workflow, agent git restrictions, commits and releases and pr draft workflow.
git-workflow-master
Git工作流专家，负责分支策略设计、合并冲突解决、代码历史维护、CI集成和团队Git规范制定.
release-steward
Prepares commit messages and release notes; commits only on explicit request.
shipper
Git and GitHub Operations — commits, pushes, PRs, issue comments.
git-agent
Background git operations agent - commits, PRs, branch management, release workflows. Runs on Sonnet to free main session.
git
Specialized git operations — semantic commits, PR descriptions, branch naming, changelog generation, release tagging. Convention-aware utility replacing ad-hoc git commands.