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 chaunsin/agent-skills --skill git-stackgit clone --depth 1 https://github.com/chaunsin/agent-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/skills/chaunsin/agent-skills/git-stack)<a href="https://agentmods.dev/skills/chaunsin/agent-skills/git-stack"><img src="https://agentmods.dev/badge/skills/chaunsin/agent-skills/git-stack/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/skills/chaunsin/agent-skills/git-stack"><img src="https://agentmods.dev/badge/skills/chaunsin/agent-skills/git-stack.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.00027 | $0.00466 |
| Opus 5.5 | $0.00011 | $0.00186 |
| Sonnet 5.5 | $0.00005 | $0.00093 |
| Haiku 4.5 | $0.00003 | $0.00047 |
Grade A, and why
git-stack 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 23d 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 stack
解决代码提交，推送，合并冲突操作。
注意 : 在开始之前需读取项目中得AGENTS.md,CLAUDE.md,README.md中得提交规范。如存在则规则优先级为: 用户提示词 > AGENTS.md > 本技能
使用场景
- 用户说：提交代码，推送代码，push代码。
- 解决代码合并冲突问题。
- 创建工作树worktree
门禁
- 相关git操作必须在有
.git/管理的目录下操作，否则退出并引导用户创建工作区或切换到对应工作区目录。 - 宿主机需要提前安装好git CLI，否则退出并引导用户安装git CLI 以及授权等.
功能列表
| 功能 | 链接 | 说明 |
|---|---|---|
| 代码提交 | ./commit | 代码提交 |
| 代码合并冲突 | ./conflict | 代码冲突解决。 |
| 工作区worktree | ./worktree | 工作区，worktree创建 |
| PR、Issues、github相关操作 | 优先使用gh操作相关技能,没有则直接使用gh命令 |
危险操作
- 永远不要更新 Git 配置
- 未经明确请求，切勿运行破坏性命令（例如 --force、硬重置）。
- 除非用户要求，否则绝不跳过钩子（--no-verify）。
- 切勿强行推送至主目录/主分支
- 如果由于钩子导致提交失败，请修复并创建新的提交（不要修改现有提交）。
- 不经请示申请，私自读取用户私钥内容如
~/.ssh/*、/root/.ssh/*、%USERPROFILE%\\.ssh、C:\\Users\\{用户名}\\.ssh\\等
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.
- 23d ago Changed · -1 lines 5000f8f7957c
- 1mo ago Changed · -1 lines a231db2a4e6c
- 1mo ago First seen · 43 lines · 27 tokens per session scan A 00739a2c7876
git-stack is a skill published in the GitHub repository chaunsin/agent-skills (2 stars, last pushed 24d ago), licensed Apache-2.0. It adds 27 tokens to every session and 466 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-09-11.
Other skills, from other repositories
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, splitting uncommitted work in a messy working tree into clean atomic commits, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple…
commit
Skill "commit" from clacky-ai/openclacky, covering smart commit skill, critical requirement: single-line commits only, core philosophy, usage and process steps.
comet-safe-delivery
A Chinese-language procedure for safely delivering specified Comet changes through Git. It covers checking worktrees and unrelated edits, staging exact files, validating hooks, and authorized commits or pushes.
devops-pipeline
Configure pre-commit hooks and lean GitHub Actions for shift-left quality assurance. Use when adding or auditing CI/CD to maximize local test coverage and minimize CI cost. Skip for Terraform/K8s, deployment pipelines, or non-GitHub CI providers.
github-pages-publish
Publish or update a static site (gh-pages) on GitHub Pages via GitHub Actions in any repo: text or pre-built HTML in, workflow set up, live URL verified. Don't use for CI test pipelines, framework/SSG builds, or Netlify/Vercel hosting.
ship
Run a release end to end, autonomous by default: version bump everywhere, changelog, docs, landing page, tag, push, GitHub release, PyPI/npm. Use to ship, cut, or tag a release. Don't use for routine commits, pull requests, or marketplace publishing.