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 ChenShuo2004/cs-skills --skill cs-github-pushgit clone --depth 1 https://github.com/ChenShuo2004/cs-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/chenshuo2004/cs-skills/cs-github-push)<a href="https://agentmods.dev/skills/chenshuo2004/cs-skills/cs-github-push"><img src="https://agentmods.dev/badge/skills/chenshuo2004/cs-skills/cs-github-push/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/chenshuo2004/cs-skills/cs-github-push"><img src="https://agentmods.dev/badge/skills/chenshuo2004/cs-skills/cs-github-push.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.00064 | $0.01003 |
| Opus 5.5 | $0.00026 | $0.00401 |
| Sonnet 5.5 | $0.00013 | $0.00201 |
| Haiku 4.5 | $0.00006 | $0.00100 |
Grade A, and why
cs-github-push 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 18d 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
CS GitHub Push
把“本地做好了”变成可核验的 GitHub 结果。处理一次明确的仓库交付：确认来源和范围、完成必要检查、提交、推送，并用远端状态证明结果。
适用边界
- 适用：推送已有改动、发布新增 skill、同步 README／文档、创建用户要求的 PR、核验某次推送是否真的到达 GitHub。
- 如果实现尚未完成，先完成实现与必要验证，再进入本流程。
- 如果还需要部署网站或应用，用
$cs-ending-time管理完整交付；本 skill 的终点是 GitHub，不把推送等同于上线。 - 用户只是询问如何推送时，解释流程即可；不要因此修改远端。
推送流程
- 确定交付目标。 找到仓库根目录、
AGENTS.md、当前分支、远端与默认分支；查看git status --short --branch、近期提交和待推送提交。明确本次要交付哪些文件，保留其他人的改动。 - 核对真实来源。 对来自另一个 Agent、工作区或补丁的内容，先找到原文件并核对完整性。对话摘要、生成日志和“已提交”的说法不能代替本地文件或 Git 对象；缺源文件时说明缺口，不凭描述重建后冒充原版。
- 完成发布前检查。 运行与改动相关的验证，检查文档链接、示例命令、生成物和敏感文件。新增或修改 CS Skills 时，同步
README.md、cs-run/SKILL.md和必要的docs/清单；README 的入口、用途、安装方式与实际目录一致。不要为一次普通代码推送重写无关文档。 - 精确提交。 查看每个待提交文件的 diff；用明确路径暂存，检查
git diff --cached --check、--stat和关键内容，再提交。不要用git add -A把无关文件带入，也不要提交密钥、私有配置、依赖目录或临时产物。 - 检查远端变化并推送。 先
git fetch，确认目标分支相对远端的状态。远端已前进时，先整合并验证，不能用强制推送覆盖。按用户指定或仓库约定选择分支；需要 PR 时推送工作分支并创建 PR。直接更新默认分支时，确认它是本次明确的目标且没有分支保护阻挡。 - 核验交付。 比对本地提交 SHA 与远端分支 SHA；如果创建 PR，记录并打开 PR 地址，核对目标分支和包含的文件。推送命令成功但未完成远端比对时，只报告“推送命令成功，远端未核验”。
决策规则
- 用户已明确要求推送本次成果，按该授权执行，不为同一动作重复求确认；新发现的其他仓库或其他任务不自动并入。
- 当前分支、目标分支或 PR 方式不明确时，先按仓库约定与用户此前选择判断；只有不同选择会改变公开结果时才提问。
- 禁止默认使用
reset --hard、push --force、删除分支或改写历史。遇到冲突、权限不足或远端拒绝，保留现场，给出具体原因与可恢复的下一步。 - 如果 GitHub 推送会触发生产部署，按项目的部署规则处理并验证生产状态；必要时转入
$cs-ending-time。
交付报告
简洁列出：仓库、目标分支或 PR、提交 SHA、推送到的远端地址、完成的验证，以及尚未交付的文件或阻塞。区分“本地提交”“分支已推送”“PR 已创建”“默认分支已更新”和“部署已验证”。
What ships with it
1 file 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.
- 18d ago Changed · -5 lines b095319f4dec
- 23d ago First seen · 43 lines · 64 tokens per session scan A 5e998bd537e2
cs-github-push is a skill published in the GitHub repository ChenShuo2004/cs-skills (204 stars, last pushed 18d ago), licensed MIT. It adds 64 tokens to every session and 1,003 once invoked, about $0.0003 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-10-02.
Other skills, from other repositories
changelog
Auto-generate a changelog from git commits and sprint data. Internal and player-facing versions.
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.
close-task-commit-push-pr
Close the active backlog task (detected from branch name), commit all changes, push to remote, and open a pull request. Use when the user says "close task and ship it", "close task commit push pr", or invokes /close-task-commit-push-pr.
git-workflow
Guided git workflows: prepare PRs, clean up branches, resolve merge conflicts, handle monorepo tags, squash-and-merge patterns. Use when asked to prepare a PR, clean branches, resolve conflicts, or tag a release.
git-push
A GitHub publishing workflow that handles first-time uploads, routine updates, and tagged releases. Git is a system for recording code changes, while GitHub hosts repositories and releases online.
development-workflow
Detailed development workflow with modular patterns for git, review, testing, and deployment.