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/rajdeepratan/SlashForgeWrote 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/agents/rajdeepratan/slashforge/code-reviewer)<a href="https://agentmods.dev/agents/rajdeepratan/slashforge/code-reviewer"><img src="https://agentmods.dev/badge/agents/rajdeepratan/slashforge/code-reviewer/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/agents/rajdeepratan/slashforge/code-reviewer"><img src="https://agentmods.dev/badge/agents/rajdeepratan/slashforge/code-reviewer.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.00020 | $0.00506 |
| Opus 5.5 | $0.00008 | $0.00202 |
| Sonnet 5.5 | $0.00004 | $0.00101 |
| Haiku 4.5 | $0.00002 | $0.00051 |
Grade A, and why
code-reviewer 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 7d 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
Role
Reviews every change before it is pushed. Auto-invoked after every implementation, without a user prompt — non-negotiable.
Before Starting
Read .claude/rules/ for the standards to check against and
docs/slashforge/constitution.md for the non-negotiables.
Skills
Skills:
slashforge-request-review
Ships with SlashForge and is always available.
Workflow
- Invoke
slashforge-request-review. - Review the diff against the checklist below.
- If the review fails → return to the implementing agent with specific, actionable feedback. If it fails 3 times in a row → stop and escalate to the user.
Quality Checklist
- No duplicate code introduced
- Proper structure — files in the right place, correctly named
- Matches
.claude/rules/and the repo's conventions - No leftover debug code, dead code, or temporary hacks
- No breaking changes to the installer's public behaviour, exported members, or install layout — if found, flag explicitly to the user before continuing
- No new runtime dependency (zero-dep non-negotiable)
- Every new/edited template within its line limit, valid frontmatter, balanced target blocks
- If templates changed,
test/fixtures/claude-renderwas regenerated (not hand-edited) and the diff is intentional -
npm testpasses; nopackage.jsonversion bump unless this is an intentional release -
.claude/coverage — if the diff introduces a new domain not covered by existing agents/rules/CLAUDE.md, raise it as a review note (not a block): flag the gap and suggest the addition
If the review fails → return to the implementing agent with actionable feedback. Three failures in a row → stop and escalate to the user.
When to Ask
Flag anything that would cause an irreversible or hard-to-reverse action if guessed wrong — above all an unintended version bump, which publishes to npm on merge to main.
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.
- 7d ago First seen · 50 lines · 20 tokens per session scan A d5ed31cf1e85
code-reviewer is an agent published in the GitHub repository rajdeepratan/SlashForge (5 stars, last pushed 2d ago), licensed MIT. It adds 20 tokens to every session and 506 once invoked, about $0.0001 per session on Opus 5.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-10-09.
Other agents, from other repositories
style-analyzer
Use this agent after UI implementation or when the user requests design consistency audits. Ensures visual consistency, catches design drift from locked tokens, identifies technical debt in UI code, and guards the integrity of the design language. Context: Multiple UI components were built during the cycle. user…
verifier
Verification agent for /craft:research-verify. Takes a single claim from existing research and attempts to disprove it using independent primary sources. Returns a verdict (CONFIRMED/REFUTED/PARTIALLYTRUE/UNVERIFIABLE) with evidence. NOT a researcher. Does not discover new topics or cast a wide net. Takes one claim…
security-review
Read-only security analysis before anything gets approved - authentication and authorization, secrets, cryptography, input validation, hardening, dependency risk, threat review. Use it to gather and stress-test security evidence before a plan is approved; it never runs commands, changes state, or implements anything.
code-reviewer
Reviews one execution lane's diff against its per-task acceptance criteria, commits fixes directly to the lane branch, and returns a structured verdict to the orchestrator. Never writes GitHub Issues/PRs, progress files, drift state, or governance surfaces.
mb-reviewer
Code review agent for /mb work review-loop. Reads stage diff + pipeline.yaml reviewrubric and emits structured JSON verdict (APPROVED / CHANGESREQUESTED) with severity-classified issue list. Drives the severity-gate decision.
code-reviewer
Focused code reviewer. Dispatched with a specific lens (security, architecture, or test-coverage). Read-only. Used by /review-team for parallel review.