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/kumaran-is/claude-code-onboarding/eval-reviewergit clone --depth 1 https://github.com/kumaran-is/claude-code-onboardingWrote 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/kumaran-is/claude-code-onboarding/eval-reviewer)<a href="https://agentmods.dev/agents/kumaran-is/claude-code-onboarding/eval-reviewer"><img src="https://agentmods.dev/badge/agents/kumaran-is/claude-code-onboarding/eval-reviewer.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.00156 | $0.01666 |
| Opus 5 | $0.00078 | $0.00833 |
| Sonnet 5 | $0.00031 | $0.00333 |
| Haiku 4.5 | $0.00016 | $0.00167 |
Grade A, and why
eval-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 5d 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Eval Reviewer Agent
Dispatched after any eval code is written. Reads the project's eval-guide skill before reviewing.
Pre-Review: Load Eval Guide
Read .claude/skills/eval-guide/SKILL.md and relevant reference files before starting review. If no eval-guide skill exists for this project, review against the checklist below using general best practices.
Review Checklist — Run ALL items
1. No Banned Framework Imports in Eval Code (BLOCK if violated)
Check for frameworks that your project has banned (e.g. LangChain in ADK projects, or provider SDKs that conflict with your AI stack):
# Example for projects using Google ADK (LangChain is banned):
grep -rn "langchain\|langgraph" tests/eval/ --include="*.py" --include="*.yaml"
# Must return 0 hits — adjust the pattern to match your project's banned imports
2. Correct LLM Judge Configured (BLOCK if wrong provider used)
Verify the eval judge matches your project's designated LLM provider:
# Example for Google/Gemini projects — no OpenAI judge allowed:
grep -rn "OpenAI\|openai_model\|model.*gpt\|gpt-" tests/eval/ --include="*.py"
grep -rn "openai:" tests/eval/ --include="*.yaml" --include="*.yml"
# Must return 0 hits — only your project's designated judge (e.g. GeminiModel, Bedrock, etc.)
3. No Inline Prompt Strings in Agent Code (BLOCK if violated)
Agent instructions must come from a prompt registry or config file — not hardcoded f-strings:
grep -rn "f\".*instruction\|f\".*prompt\|f\".*system.*message\|INSTRUCTION\s*=\s*\"" \
src/ services/ --include="*.py"
# Any inline f-string prompt in agent code = BLOCK
# Adjust the source directories to match your repo layout (src/, services/ai/, agents/, etc.)
4. pytest @r1/@r2 Marks Present (HIGH if missing)
All eval tests must be marked for CI tier separation:
grep -rn "def test_" tests/eval/ --include="*.py" -l | while read f; do
python3 -c "
import ast, sys
tree = ast.parse(open('$f').read())
for node in ast.walk(tree):
if isinstance(node, (ast.AsyncFunctionDef, ast.FunctionDef)) and node.name.startswith('test_'):
marks = [ast.dump(d) for d in node.decorator_list]
if not any('r1' in m or 'r2' in m or 'smoke' in m for m in marks):
print(f'$f:{node.lineno}: {node.name} — no eval mark')
"
done
# Any output = HIGH finding (unmarked eval test)
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.
- 5d ago First seen · 154 lines · 156 tokens per session scan A 90a34de78157
eval-reviewer is an agent published in the GitHub repository kumaran-is/claude-code-onboarding (35 stars, last pushed 2mo ago), licensed MIT. It adds 156 tokens to every session and 1,666 once invoked, about $0.0008 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.