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/firatcand/forge/reviewnpx skills add firatcand/forge --skill reviewgit clone --depth 1 https://github.com/firatcand/forgeWrote 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/skills/firatcand/forge/review)<a href="https://agentmods.dev/skills/firatcand/forge/review"><img src="https://agentmods.dev/badge/skills/firatcand/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 | $0.00032 | $0.00663 |
| Opus 5 | $0.00016 | $0.00331 |
| Sonnet 5 | $0.00006 | $0.00133 |
| Haiku 4.5 | $0.00003 | $0.00066 |
Grade A, and why
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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/review
Preflight: worktree guard
Task-scoped mutating skill — must run from a worktree, not the main checkout. Contract: skills/_shared/worktree-guard.md.
TOPLEVEL="$(git rev-parse --show-toplevel 2>/dev/null || echo '')"
if [ -z "$TOPLEVEL" ]; then
echo "✗ worktree-guard: not inside a git repository" >&2
exit 1
fi
BRANCH="$(git branch --show-current 2>/dev/null || echo '')"
DEFAULT_BRANCH="$(git symbolic-ref --short refs/remotes/origin/HEAD 2>/dev/null | sed 's@^origin/@@' || echo 'main')"
if [ -f "$TOPLEVEL/.forge/worktree-task.json" ]; then
echo "✓ worktree-guard: $TOPLEVEL ($BRANCH)"
elif [ "$BRANCH" = "${DEFAULT_BRANCH:-main}" ]; then
echo "✗ worktree-guard: refusing to run on default branch '$BRANCH' from $TOPLEVEL" >&2
echo " Parallel Claude Code sessions on the main checkout clobber each other's HEAD." >&2
echo " → cd into an existing worktree, or run /pickup-task to create one." >&2
exit 1
else
echo "⚠ worktree-guard: no .forge/worktree-task.json at $TOPLEVEL (branch: $BRANCH)" >&2
echo " Proceeding, but this worktree may be manually-created or stale." >&2
fi
Process
- Run
git diff main...HEADto get current diff - Always invoke
code-reviewersubagent - If diff touches paths in CRITICAL.md, invoke
security-auditor - If task type is "design" or "frontend", invoke
design-reviewer - If diff touches paths in CRITICAL.md AND
.forge/settings.yamlhasagents.review_host_cliset (notnull): tell the user to run/second-opinion review-implfor an out-of-process, different-model-lineage check (or, if Claude is driving, invoke the slash command directly via the host's skill loader — skills are markdown commands, not shell binaries, so aBash(/second-opinion ...)call will fail). Skip silently ifreview_host_cliisnull(adopter opted out). - Aggregate findings across all reviewers (in-process subagents +
/second-opinionverdict); categorize by severity (block / improvement / nit)./second-opinionseverity: blockfindings count toward the block bucket. - Print summary; ask user to address blocks before /ship
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.
- 5d ago First seen · 47 lines · 32 tokens per session scan A dfff27a706b0
review is a skill published in the GitHub repository firatcand/forge (13 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 663 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-30.
Other skills, from other repositories
ospec-change
Create or advance a lightweight OSpec change using the classic fast workflow.
prospec-knowledge-generate
Generate AI Knowledge - Read raw-scan.md, analyze project structure, autonomously decide module boundaries, and produce Recipe-First module READMEs and index. Triggers: generate knowledge, analyze project, module split, 產生知識, 知識庫, 分析專案, 模組拆分.
submit-pr
Open a prospec pull request in the house format — push the change's two commits, write the Traditional Chinese body, and link it to its issue. Triggers: submit pr, open pr, 開 PR, 送 PR, 發 PR, pull request, 提交 PR.
prospec-explore
Explore - Requirement exploration, problem investigation, and solution comparison partner. Triggers: explore, compare, investigate, unsure, clarify, 探索, 比較, 釐清, 調查, 不確定.
prospec-plan
Plan Implementation - Convert User Story into technical implementation plan (plan.md) and change specification (delta-spec.md). Triggers: plan, architecture, technical plan, 規劃, 架構規劃, 技術規劃.
prospec-knowledge-update
Incremental Knowledge Update - Parse delta-spec.md to identify affected modules, scan source code, and update module README, index.md, and module-map.yaml incrementally. Triggers: knowledge update, incremental update, sync knowledge, update docs, 更新知識, 增量更新, 同步知識, 更新文件.