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/RapierCraftStudios/ForgeDockWrote 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/rapiercraftstudios/forgedock/review-pr-staging)<a href="https://agentmods.dev/commands/rapiercraftstudios/forgedock/review-pr-staging"><img src="https://agentmods.dev/badge/commands/rapiercraftstudios/forgedock/review-pr-staging/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/rapiercraftstudios/forgedock/review-pr-staging"><img src="https://agentmods.dev/badge/commands/rapiercraftstudios/forgedock/review-pr-staging.svg" alt="Reviewed on agentmods" width="80" 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.13831 |
| Opus 5.5 | $0.00006 | $0.05532 |
| Sonnet 5.5 | $0.00003 | $0.02766 |
| Haiku 4.5 | $0.00001 | $0.01383 |
Grade B, and why
review-pr-staging scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
type forge_resolve >/dev/null 2>&1 || { setopt nonomatch 2>/dev/null || true; FORGE_SOURCED_ROOT='${CLAUDE_PLUGIN_ROOT}'; for _r in "$(cygpath -u "${FORGEDOCK_HOME:-}" 2>/dev/null || printf %s "${FORGEDOCK_HOME:-}")" '${ The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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 Changed · -747 lines e028fa7afad1
- 4d ago Changed · +5 lines 5181bbde4961
- 10d ago Changed · +25 lines 12cb126d3289
- 12d ago Changed · -300 lines 8133080328e0
- 13d ago Changed · +352 lines scan A → B f9088ddc506a
- 14d ago Changed · +218 lines 5c8141789dac
- 15d ago Changed · +22 lines 60315f734dfc
- 17d ago Changed · +9 lines 3d61734ec50e
- 1mo ago First seen · 956 lines · 14 tokens per session scan A ad9137827cf6
review-pr-staging is a command published in the GitHub repository RapierCraftStudios/ForgeDock (119 stars, last pushed yesterday), licensed AGPL-3.0. It adds 14 tokens to every session and 13,831 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
review-deep
Review change vs spec, plan, code quality heuristics, and repo rules; append remediation phase if needed.
validate-pr-description
Use when validating a PR title and description for conventional commit format, issue linking keywords, and template compliance before submission.
review-remote
Review open PR/MR and publish findings.
pr
Create/update PR/MR title and description.
review-branch
Review an existing branch holistically before merging — blast radius, conventions, security, and spec compliance.