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/razaib-khan/forgeweave/forge-commitgit clone --depth 1 https://github.com/Razaib-khan/ForgeWeaveWhat 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.00010 | $0.00187 |
| Opus 5 | $0.00005 | $0.00093 |
| Sonnet 5 | $0.00002 | $0.00037 |
| Haiku 4.5 | $0.00001 | $0.00019 |
Grade A, and why
forge-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
Forge Commit
Analyze the staged changes and generate a Conventional Commit message.
- Run
!{git diff --staged}to inspect changes - Determine commit type from:
feat | fix | docs | style | refactor | perf | test | build | ci | chore | revert - Determine scope from the modified files (e.g.,
cli,server,templates) - Write a concise description (50 chars max, imperative mood)
- Add a detailed body explaining what and why (wrap at 72 chars)
Format:
<type>(<scope>): <description>
<optional body>
<optional footer>
If no changes are staged, notify the user and list unstaged files.
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 · 26 lines · 10 tokens per session scan A 197ecb471782
forge-commit is a command published in the GitHub repository Razaib-khan/ForgeWeave (1 stars, last pushed 2mo ago), licensed MIT. It adds 10 tokens to every session and 187 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 commands, from other repositories
port-commits
把已落地、可追溯的一组 commit，用 cherry-pick（最稳妥） 同步到目标分支（常见：main → hc-0730）。.
align
Context-aware alignment. When in plan mode, it reviews the active plan. Otherwise, it reviews all branch changes against Ion quality gates and principles, implements the fixes and commits them after operator approval.
squash
Rebuild a feature branch into clean conventional commits while preserving its exact final tracked tree.
git-push-all
Stages all changes, commits them, and pushes to the remote repository.
commit
Commit changes with logical grouping.
r-util-rel-squash
Generate a squash plan for the current release branch by grouping.