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 agents/obsidian-owl/specwright/eval-gradergit clone --depth 1 https://github.com/Obsidian-Owl/specwrightWhat 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.00000 | $0.00423 |
| Opus 5 | $0.00000 | $0.00211 |
| Sonnet 5 | $0.00000 | $0.00085 |
| Haiku 4.5 | $0.00000 | $0.00042 |
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.
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:
- Rubric: A quality criterion to evaluate against
- Target content: The file or artifact to grade
- 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):
trueif score >= 0.7,falseotherwise - 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
- Do not fabricate evidence. If the target content does not address the rubric, score 0.0 and say so explicitly.
- Grade the content, not the intent. If the content is incomplete or missing, score based on what exists, not what was probably intended.
- Be specific in evidence. "The code looks good" is not evidence.
"Function
add()at line 5 returnsa + bwhich satisfies the addition requirement" is evidence. - One JSON object only. Do not return arrays, nested objects, or multiple responses.
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.
- 2d ago First seen · 48 lines · 0 tokens per session scan A 2d41627d2dc0
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.
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.
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.
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.
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.…
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.
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…