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 commands/richkuo/rk-skills/commitgit clone --depth 1 https://github.com/richkuo/rk-skillsWhat 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.00009 | $0.00197 |
| Opus 5 | $0.00005 | $0.00098 |
| Sonnet 5 | $0.00002 | $0.00039 |
| Haiku 4.5 | $0.00001 | $0.00020 |
Grade A, and why
commit 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 2d 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
Create a git commit using the Haiku model following these steps:
- Run git status and git diff to see all changes
- Run git log to understand the commit message style
- Analyze all staged and unstaged changes
- Draft a concise commit message focusing on the "why" rather than the "what"
- Add relevant untracked files to staging if needed
- Create the commit with the message using a HEREDOC for proper formatting
- Run git status after to verify success
Important:
- Do not commit files that likely contain secrets (.env, credentials.json, etc)
- If pre-commit hooks modify files, verify it's safe to amend
- Do not push unless explicitly asked
- Use the format:
git commit -m "$(cat <<'EOF'\nCommit message here.\nEOF\n)"
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.
- 2d ago First seen · 22 lines · 9 tokens per session scan A 256b2ed0e42f
commit is a command published in the GitHub repository richkuo/rk-skills (49 stars, last pushed 3d ago), licensed MIT. It adds 9 tokens to every session and 197 once invoked, about $0.0000 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-30.
Other commands, from other repositories
git-pr-push
Create git commit and push branch as PR using git + GitHub CLI.
pr-submit
Create git commit and submit current branch with Graphite (squashes commits and rebases stack).
commit
Create a local git commit for source skills without pushing.
contradiction-analysis
用矛盾分析法识别主要矛盾、主要方面和处理方向。.
criticism-self-criticism
用批评与自我批评方法对已完成工作做结构化审查。.
mass-line
用群众路线收集多源信息、整合反馈并返回验证。.