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/guanyang/open-agent-hub/commitgit clone --depth 1 https://github.com/guanyang/open-agent-hubWhat 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.00028 | $0.00264 |
| Opus 5 | $0.00014 | $0.00132 |
| Sonnet 5 | $0.00006 | $0.00053 |
| Haiku 4.5 | $0.00003 | $0.00026 |
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 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
Slash Command: /commit
Core Objective
Analyze staged git modifications and generate/write a high-quality Semantic Commit message.
Steps for the Agent
- Analyze Staged Changes: Run
git diff --cachedto inspect what changes have been staged. - Determine Conventional Commit Type:
feat: New features (e.g., new skill, agent, command, utility).fix: Bug fixes.docs: Documentation updates.refactor: Code restructurings.chore: Maintenance, dependencies, config updates.
- Format Subject & Body:
- Write a concise summary line (subject) under 50 characters.
- Formulate a structured commit message body detailing Added, Modified, and Deleted resources.
- Action: Write the generated message directly to
.git/COMMIT_EDITMSG. - Output: Output the commit message for the user to review, and tell them they can run
git commit -F .git/COMMIT_EDITMSGto finalize the commit.
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 · 24 lines · 28 tokens per session scan A c5af76eb095f
commit is a command published in the GitHub repository guanyang/open-agent-hub (958 stars, last pushed yesterday), licensed MIT. It adds 28 tokens to every session and 264 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-30.
Other commands, from other repositories
new-skill
Scaffold a new hr- skill directory with SKILL.md, content/, and examples/ templates.
release-check
Run pre-release build, test, typecheck, validation, and lint checks.
validate
Run repository validation and markdown linting for SKILL.md files.
sync-and-validate
Run sync, validate, and markdown lint after editing skills.
freedom-of-movement
/volumes/vixinssd/wizardsoftheghosts/generated/openclaw/freedom-of-movement/SKILL.md.
greater-invisibility
/volumes/vixinssd/wizardsoftheghosts/generated/openclaw/greater-invisibility/SKILL.md.