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 phanghonghao/THU-Awesome-Skills --skill git-pushgit clone --depth 1 https://github.com/phanghonghao/THU-Awesome-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/phanghonghao/thu-awesome-skills/git-push)<a href="https://agentmods.dev/skills/phanghonghao/thu-awesome-skills/git-push"><img src="https://agentmods.dev/badge/skills/phanghonghao/thu-awesome-skills/git-push.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.00028 | $0.01020 |
| Opus 5 | $0.00014 | $0.00510 |
| Sonnet 5 | $0.00006 | $0.00204 |
| Haiku 4.5 | $0.00003 | $0.00102 |
Grade A, and why
git-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 7d 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Push Skill
Quickly commit and push git changes to GitHub.
Workflow
Step 1: Ask User for Description
FIRST: Ask the user to provide their own description for this commit:
请输入本次提交的描述（简短说明你做了什么改动）：
Step 2: Ask about README.md update
Ask the user:
是否需要更新 GitHub 首页 README.md？
如果需要，请提供素材目录路径（包含 gif、reward 趋势图等）：
（留空跳过，默认路径示例：RTX6000\Magicbot_Z1\docs\github_readme）
If the user provides a path:
- Read the current
README.mdat the repo root - List all files in the provided素材目录 (gifs, pngs, etc.)
- Compare with what's already referenced in README.md
- Propose updates to README.md (new images, updated sections, etc.)
- Apply the changes after user confirms
This step runs in parallel with Step 3 (git status check).
Step 3: Check git status
Run git status and git diff --stat to see what files have changed.
Step 4: List Changes for Confirmation
Clearly display what will be uploaded:
=== 将要上传的更改 ===
新增文件:
- file1.ext
- file2.ext
修改文件:
- file3.ext
- file4.ext
删除文件:
- file5.ext
=== AI 生成的总结 ===
[AI's summary of changes]
请确认是否上传？(yes/no)
Wait for user confirmation before proceeding.
Step 5: Add and Commit
After user confirms:
-
Add relevant files:
- DO add: source code (.py, .js, .md, etc.), data files (.csv), images/docs
- DON'T add: pycache, venv, node_modules, .claude, .git, etc.
-
Create commit with combined message format:
(User's description), (AI's summary)
- [key change 1]
- [key change 2]
Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
Example:
修复笔记图片显示问题, 更新材料加工笔记结构和图片路径
- 图片重命名为 English_Pinyin 格式
- 更新 MD 和 HTML 中的图片引用路径
- 修复 3_17.html 图片不显示问题
Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
Step 6: Check for Open PRs (gate before push)
Before pushing, check for open Pull Requests using gh pr list:
gh pr list --state open
If there are open PRs:
- Display each PR with title, author, and clickable URL
- Ask user:
检测到以下 PR 尚未处理，请选择操作：- For each PR, offer:
merge/close/skip (稍后处理)
- For each PR, offer:
- If user chooses
merge: rungh pr merge <number> --merge - If user chooses
close: rungh pr close <number> - If user chooses
skip: abort the push, tell user to handle PR first - After all PRs resolved → continue to Step 7
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.
- 7d ago First seen · 144 lines · 28 tokens per session scan A bbd6411a56cc
git-push is a skill published in the GitHub repository phanghonghao/THU-Awesome-Skills (8 stars, last pushed 28d ago), licensed MIT. It adds 28 tokens to every session and 1,020 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 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…