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/sangrokjung/claude-forge/evalgit clone --depth 1 https://github.com/sangrokjung/claude-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/commands/sangrokjung/claude-forge/eval)<a href="https://agentmods.dev/commands/sangrokjung/claude-forge/eval"><img src="https://agentmods.dev/badge/commands/sangrokjung/claude-forge/eval.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.00014 | $0.00627 |
| Opus 5 | $0.00007 | $0.00313 |
| Sonnet 5 | $0.00003 | $0.00125 |
| Haiku 4.5 | $0.00001 | $0.00063 |
Grade A, and why
eval 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 4d 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Eval Command
Manage eval-driven development workflow.
Usage
/eval [define|check|report|list] [feature-name]
Define Evals
/eval define feature-name
Create a new eval definition:
- Create
.claude/evals/feature-name.mdwith template:
## EVAL: feature-name
Created: $(date)
### Capability Evals
- [ ] [Description of capability 1]
- [ ] [Description of capability 2]
### Regression Evals
- [ ] [Existing behavior 1 still works]
- [ ] [Existing behavior 2 still works]
### Success Criteria
- pass@3 > 90% for capability evals
- pass^3 = 100% for regression evals
- Prompt user to fill in specific criteria
Check Evals
/eval check feature-name
Run evals for a feature:
- Read eval definition from
.claude/evals/feature-name.md - For each capability eval:
- Attempt to verify criterion
- Record PASS/FAIL
- Log attempt in
.claude/evals/feature-name.log
- For each regression eval:
- Run relevant tests
- Compare against baseline
- Record PASS/FAIL
- Report current status:
EVAL CHECK: feature-name
========================
Capability: X/Y passing
Regression: X/Y passing
Status: IN PROGRESS / READY
Report Evals
/eval report feature-name
Generate comprehensive eval report:
EVAL REPORT: feature-name
=========================
Generated: $(date)
CAPABILITY EVALS
----------------
[eval-1]: PASS (pass@1)
[eval-2]: PASS (pass@2) - required retry
[eval-3]: FAIL - see notes
REGRESSION EVALS
----------------
[test-1]: PASS
[test-2]: PASS
[test-3]: PASS
METRICS
-------
Capability pass@1: 67%
Capability pass@3: 100%
Regression pass^3: 100%
NOTES
-----
[Any issues, edge cases, or observations]
RECOMMENDATION
--------------
[SHIP / NEEDS WORK / BLOCKED]
List Evals
/eval list
Show all eval definitions:
EVAL DEFINITIONS
================
feature-auth [3/5 passing] IN PROGRESS
feature-search [5/5 passing] READY
feature-export [0/4 passing] NOT STARTED
Arguments
$ARGUMENTS:
define <name>- Create new eval definitioncheck <name>- Run and check evalsreport <name>- Generate full reportlist- Show all evalsclean- Remove old eval logs (keeps last 10 runs)
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.
- 4d ago First seen · 125 lines · 14 tokens per session scan A 54f4d3f6daf2
eval is a command published in the GitHub repository sangrokjung/claude-forge (822 stars, last pushed yesterday), licensed MIT. It adds 14 tokens to every session and 627 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-30.
Other commands, from other repositories
speckit.implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
docs-review
Phase 4 of documenting-projects: Quality gate with 8 measurable criteria and iteration. Triggers: '/docs-review', invoked by documenting-projects orchestrator.
memcord-save-progress
Auto-summarize and save conversation progress.
audit-strict
Multi-pass consensus audit — runs the audit twice with different prompts, only reports consensus findings. Aggressively cuts false positives.
define-events
Produces instrumentation specification with events, properties, owners, and QA steps.
hypothesis
Generate hypotheses and define how to test them.