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.
git clone --depth 1 https://github.com/Razaib-khan/ForgeWeaveWrote 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/commands/razaib-khan/forgeweave/forge-review)<a href="https://agentmods.dev/commands/razaib-khan/forgeweave/forge-review"><img src="https://agentmods.dev/badge/commands/razaib-khan/forgeweave/forge-review.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.00014 | $0.00140 |
| Opus 5 | $0.00007 | $0.00070 |
| Sonnet 5 | $0.00003 | $0.00028 |
| Haiku 4.5 | $0.00001 | $0.00014 |
Grade A, and why
forge-review 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 6d 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 Review
Review the staged changes (or specified files) for:
- Code quality issues
- Potential bugs
- Security vulnerabilities
- Performance concerns
- Edge cases and error handling
- Documentation completeness
Format output as a structured checklist with severity levels:
[CRITICAL] Issue with explanation and fix suggestion
[HIGH] Issue with explanation
[MEDIUM] Issue with explanation
[LOW] Suggestion with explanation
Provide specific remediation suggestions with code examples where applicable.
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.
- 6d ago First seen · 27 lines · 14 tokens per session scan A c4c902fb9fc3
forge-review is a command published in the GitHub repository Razaib-khan/ForgeWeave (1 stars, last pushed 2mo ago), licensed MIT. It adds 14 tokens to every session and 140 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
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.
resolve-dependabot-prs
Triage open Dependabot PRs, return a quick risk/action summary table, then enter planning mode with an ordered rebase→merge→follow-up→resume resolution plan.
auto-review
A code-review command that evaluates changed code against the TRUST 5 criteria.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
auto-verify
A command for checking a website's front-end user experience with Playwright, a tool that automates web browsers.
advanced-code-review-context
Advanced Code Review Phase 2: Context Analysis - load previous reviews, PR history, declined items.