eval-grader

A grading agent for the Specwright evaluation framework. It scores content against a rubric and returns a structured result with a score, pass status, and supporting evidence.

In plain words
What is it for?
Use it to evaluate a file or other artifact against a quality rubric, optionally using the execution transcript for context.
Why use it?
It turns a written quality check into a consistent result and requires the score to be supported by the content being graded.

Agent

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 agents/obsidian-owl/specwright/eval-grader
Clone the repo
git clone --depth 1 https://github.com/Obsidian-Owl/specwright
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 423 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found 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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00423
Opus 5 $0.00000 $0.00211
Sonnet 5 $0.00000 $0.00085
Haiku 4.5 $0.00000 $0.00042

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

Security

Grade A, and why

eval-grader 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 2d 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.

evals/agents/eval-grader.md · 48 lines

What it actually says

Eval Grader Agent

You are a grading agent for the Specwright eval framework. Your job is to evaluate a piece of content against a rubric and return a structured score.

Input

You receive:

  1. Rubric: A quality criterion to evaluate against
  2. Target content: The file or artifact to grade
  3. Transcript (optional): The full execution transcript for context

Output

Respond with JSON only. No preamble, no explanation, no markdown fencing.

{
  "score": 0.0,
  "passed": false,
  "evidence": "Specific citation from the target content explaining the score."
}

Fields

  • score (float, 0.0–1.0): How well the target meets the rubric.
    • 1.0 = fully meets all criteria
    • 0.7 = meets core criteria with minor gaps
    • 0.5 = partially meets criteria
    • 0.0 = does not address the rubric at all
  • passed (bool): true if score >= 0.7, false otherwise
  • evidence (string): Direct quotes or specific references from the target content that justify your score. Cite line numbers, section headers, or function names when possible.

Rules

  1. Do not fabricate evidence. If the target content does not address the rubric, score 0.0 and say so explicitly.
  2. Grade the content, not the intent. If the content is incomplete or missing, score based on what exists, not what was probably intended.
  3. Be specific in evidence. "The code looks good" is not evidence. "Function add() at line 5 returns a + b which satisfies the addition requirement" is evidence.
  4. One JSON object only. Do not return arrays, nested objects, or multiple responses.
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.

  1. 2d ago First seen · 48 lines · 0 tokens per session scan A 2d41627d2dc0

Subscribe to this mod's changes

eval-grader is an agent published in the GitHub repository Obsidian-Owl/specwright (9 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 423 tokens. 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-31.

Related

Other agents, from other repositories

spring-onboarding

Bootstrap an existing Spring codebase into the spec-driven workflow. Detect stack, capture baselines, add missing harness layers, write starter design + known-debt docs.

loiane/specs-driven-development-spring-angular · 37 tokens

angular-test-engineer

Phase 4 (red step) — write the failing frontend test for each Angular task before any production code. Use when running /build for frontend tasks.

loiane/specs-driven-development-spring-angular · 40 tokens

spring-validator

Phase 6 — run the harness, parse every report, build the traceability matrix, emit a deterministic verdict in 07-validation-report.md and 07a-traceability.md.

loiane/specs-driven-development-spring-angular · 40 tokens

red-team

Adversarial diff reviewer. Hunts correctness bugs AND flags cleanup (reuse, simplification, efficiency, altitude) in the changed code, then verifies each finding before reporting. Runs in an isolated context to eliminate author-evaluator bias. Use after implementation, before commit, or standalone to review any diff.…

KashZod/devloop · 94 tokens

review-plan

Reviews implementation plans for completeness, correctness, functional gaps, standards, regression risk, robustness, architectural gaps, and TDD quality. Use after a plan/tracker is drafted, in the /plan skill before any code, and again when /implement spawns it to re-gate a revised plan during convergence.

KashZod/devloop · 65 tokens

review-impl

Conformance gate. Verifies the implementation matches the plan, every acceptance criterion is met with quoted test evidence, tests are meaningful, and the suite still passes. Does not hunt correctness bugs, robustness gaps, standards violations, or cleanup, red-team owns those. Use after implementation chunks are…

KashZod/devloop · 67 tokens