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 skills/garyfigno/dr.wangagent/git-commitnpx skills add GaryFigno/Dr.WangAgent --skill git-commitgit clone --depth 1 https://github.com/GaryFigno/Dr.WangAgentWhat 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.00042 | $0.00418 |
| Opus 5 | $0.00021 | $0.00209 |
| Sonnet 5 | $0.00008 | $0.00084 |
| Haiku 4.5 | $0.00004 | $0.00042 |
Grade A, and why
git-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 yesterday.
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 status --short git diff --stat -
检查是否混入了不该提交的东西（密钥、构建产物、日志）。发现
config.yaml、.env、credentials.json、dist/、build/等，先让用户确认，不要自行加入。 -
按改动写提交信息，格式：
<type>(<scope>): <中文简述>feat新功能fix修 bugrefactor重构（不改行为）docs文档test测试chore杂务（依赖、构建、格式化）
scope 是可选的影响模块，如
feat(quest): 步骤失败自动重试。 -
一次提交只做一件事：改动跨多个无关主题时，用
git add <path>分开提交。 -
提交前展示命令让用户确认（除非已获授权直接执行）：
git commit -m "<message>"
红线
- 提交前必须
git status确认暂存区范围 - 不提交
.git、node_modules、.venv、dist/、build/、密钥与日志文件 - 不替用户改写他人未提交的改动
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.
- yesterday First seen · 44 lines · 42 tokens per session scan A 68d3d2ea9c9b
git-commit is a skill published in the GitHub repository GaryFigno/Dr.WangAgent (2 stars, last pushed 13d ago), licensed MIT. It adds 42 tokens to every session and 418 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
cut-release
Decide whether unreleased develop work warrants a release, pick the version per semver.org, and cut it following this repo's established commit/PR/tag/release pattern.
openspec-explore
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
openspec-apply-change
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
openspec-archive-change
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
openspec-propose
Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.
openspec-sync-specs
Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.