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 skills add 2428424081cn/Skill-mcp --skill git-workflow-progit clone --depth 1 https://github.com/2428424081cn/Skill-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/2428424081cn/skill-mcp/git-workflow-pro)<a href="https://agentmods.dev/skills/2428424081cn/skill-mcp/git-workflow-pro"><img src="https://agentmods.dev/badge/skills/2428424081cn/skill-mcp/git-workflow-pro.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.1 | $0.00047 | $0.00303 |
| Opus 5 | $0.00023 | $0.00151 |
| Sonnet 5 | $0.00009 | $0.00061 |
| Haiku 4.5 | $0.00005 | $0.00030 |
Grade A, and why
git-workflow-pro 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 6d 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
Git 规范化工作流指南 (Git Workflow Pro)
当需要提交代码、整理提交历史、检查未跟踪文件或排查冲突时，遵循本工作流。
核心工作流
第一步：分析代码变动
运行分析脚本提取工作区与暂存区的变动摘要：
node scripts/analyze_git_diff.mjs
第二步：生成规范提交信息 (Conventional Commits)
遵循如下提交格式：
<type>(<scope>): <subject>
<body>
<footer>
Type 类型标准：
feat: 新增功能fix: 修复缺陷docs: 文档变动style: 不影响代码逻辑的代码格式变动refactor: 重构代码（非新功能、非缺陷修复）perf: 性能优化test: 测试用例增改chore: 构建流程或辅助工具变动
第三步：提交前代码自检
node scripts/check_staged_rules.mjs
What ships with it
4 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.
- 6d ago First seen · 42 lines · 47 tokens per session scan A b39e6d36c702
git-workflow-pro is a skill published in the GitHub repository 2428424081cn/Skill-mcp (1 stars, last pushed 13d ago), licensed MIT. It adds 47 tokens to every session and 303 once invoked, about $0.0002 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
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for prisma-next. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
git-commit
Creates git commits following Conventional Commits format with type/scope/subject and detailed markdown body. Use when user wants to commit changes, create commit, save work, or stage and commit. Enforces project-specific conventions from CLAUDE.md. Each change type gets its own markdown heading (# emoji + type), with…