A command for checking an implementation against stated acceptance criteria. Acceptance criteria are the conditions a feature or fix must satisfy.

Use it to define criteria, run relevant tests, collect evidence, calculate a result, and report the outcome with a breakdown by criterion.

It provides structured evidence about whether the work is complete and how well it meets the requirements. It can use pass-or-fail, numeric, or category-based scoring.

eval — Command by fmflurry

Install

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.

agentmods

npx agentmods add commands/fmflurry/settings-opencode/eval

Clone the repo

git clone --depth 1 https://github.com/fmflurry/settings-opencode

Per session 5 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 445 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin 89% copy Near-identical to another mod in the catalogue.

Token cost

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.00005	$0.00445
Opus 5	$0.00003	$0.00222
Sonnet 5	$0.00001	$0.00089
Haiku 4.5	$0.00001	$0.00044

Measured yesterday against content hash 2b4eed9ccc69, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 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.

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.

Origin

This is a copy

89% identical to eval — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

commands/eval.md · 89 lines

What it actually says

Eval Command

Evaluate implementation against acceptance criteria: $ARGUMENTS

Your Task

Run structured evaluation to verify the implementation meets requirements.

Evaluation Framework

Grader Types

Binary Grader - Pass/Fail
- Does it work? Yes/No
- Good for: feature completion, bug fixes
Scalar Grader - Score 0-100
- How well does it work?
- Good for: performance, quality metrics
Rubric Grader - Category scores
- Multiple dimensions evaluated
- Good for: comprehensive review

Evaluation Process

Step 1: Define Criteria

Acceptance Criteria:
1. [Criterion 1] - [weight]
2. [Criterion 2] - [weight]
3. [Criterion 3] - [weight]

Step 2: Run Tests

For each criterion:

Execute relevant test
Collect evidence
Score result

Step 3: Calculate Score

Final Score = Σ (criterion_score × weight) / total_weight

Step 4: Report

Evaluation Report

Overall: [PASS/FAIL] (Score: X/100)

Criterion Breakdown

Criterion	Score	Weight	Weighted
[Criterion 1]	X/10	30%	X
[Criterion 2]	X/10	40%	X
[Criterion 3]	X/10	30%	X

Evidence

Criterion 1: [Name]

Test: [what was tested]
Result: [outcome]
Evidence: [screenshot, log, output]

Recommendations

[If not passing, what needs to change]

Pass@K Metrics

For non-deterministic evaluations:

Run K times
Calculate pass rate
Report: "Pass@K = X/K"

TIP: Use eval for acceptance testing before marking features complete.

Changes

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 First seen · 89 lines · 5 tokens per session scan A 2b4eed9ccc69

Subscribe to this mod's changes

eval is a command published in the GitHub repository fmflurry/settings-opencode (172 stars, last pushed 19d ago), licensed MIT. It adds 5 tokens to every session and 445 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to eval, differing in 2 lines, and is treated as a copy.

Testing

eval