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 skills add tikalk/adlc-team-skills --skill evals-implementgit clone --depth 1 https://github.com/tikalk/adlc-team-skillsWrote 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/skills/tikalk/adlc-team-skills/evals-implement)<a href="https://agentmods.dev/skills/tikalk/adlc-team-skills/evals-implement"><img src="https://agentmods.dev/badge/skills/tikalk/adlc-team-skills/evals-implement.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.1 | $0.00030 | $0.01234 |
| Opus 5 | $0.00015 | $0.00617 |
| Sonnet 5 | $0.00006 | $0.00247 |
| Haiku 4.5 | $0.00003 | $0.00123 |
Grade A, and why
evals-implement 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 8d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
evals-implement
What this skill does
Generates the complete executable evaluation implementation following EDD Principle VIII (Close Production Loop) from the published goldset, with automated unit testing to verify evaluator correctness.
Output:
- Grader/Metric Implementation - Python evaluators for each goldset criterion with binary pass/fail
- PromptFoo: Python grader functions with JSON output in
evals/{system}/graders/ - DeepEval: Custom metric classes inheriting from
BaseMetric
- PromptFoo: Python grader functions with JSON output in
- Evaluator Unit Tests - Automated tests (
evals/{system}/tests/test_check_*.py) that run the goldset pass/fail examples against the generated graders to ensure the evaluator itself is accurate - Evaluation Configuration - Complete config file (
config.jsorconfig.py) with Tier 1 + Tier 2 evaluation structure - Auto-handoff to
/evals-validateto run validation
Key EDD Principles Applied:
- Principle VIII: Close Production Loop - Failure type gates route to appropriate actions
- Principle II: Binary Pass/Fail - Ensure graders return strictly 1.0 (pass) or 0.0 (fail)
- Principle IX: Test Data as Code - Unit test generated code against dataset examples
When to use
- After
/evals-clarify: Convert accepted goldset criteria into executable code - Regenerating configs: Re-build evaluator suite after adding new goldset criteria
- Adding unit tests: Hardening the evaluator itself against regression or bugs
When NOT to use
- Goldset not published: Run
/evals-clarifyto generategoldset.jsonfirst - Running evaluations: Use
/evals-validateto run the suite against application outputs
Process
User Input
$ARGUMENTS
--system SYSTEM— Override active evaluation framework (promptfooordeepeval)--no-tests— Skip automated unit test generation for graders (not recommended)
Execution Steps
Phase 1: Trace-to-Grader Synthesis (Automated Eval Engineering)
- Reads
evals/{system}/goldset.json. - Maps rich evidence fields from the goldset criteria into grader logic (Trace-to-Grader Synthesis):
- Uses
pass_conditionandfail_conditionas the grader's core rubric. - Extracts pass/fail examples to act as raw data anchors and few-shot classification anchors inside the grader logic.
- Injects
Root Cause Analysisandaxial_codingnotes as contextual prompt guidelines or regex patterns to catch exact failure manifestations.
- Uses
- For PromptFoo: Generates Python grader functions (
evals/{system}/graders/check_*.py) containing specialized, dynamic LLM-judge templates or regex checks compiled from these goldset inputs. - For DeepEval: Generates Custom Metric classes inheriting from
BaseMetriccompiled from these goldset inputs. - All graders conform strictly to the binary pass/fail standard (returning only
1.0or0.0, with zero Likert scale leakage).
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 86 lines · 30 tokens per session scan A 4ee6425d6061
evals-implement is a skill published in the GitHub repository tikalk/adlc-team-skills (132 stars, last pushed today), licensed MIT. It adds 30 tokens to every session and 1,234 once invoked, about $0.0002 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 skills, from other repositories
gentle-ai-bench
Trigger: bench, journey, journeys, driven mode, gentle-ai-bench, journey corpus, j-numbers, bench axis. Author and verify gentle-ai bench journeys; go test ./bench never proves driven execution.
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
memstack-development-test-writer
Use this skill when the user says 'write tests', 'add tests', 'test coverage', 'unit tests', 'integration tests', 'component tests', 'mocking', 'edge cases', or needs to generate tests with proper mocking and edge case coverage. Do NOT use for refactoring plans or database migrations.
verify
Runs this project's check chain through scripts/verify.py and reads the receipt it writes. Fires when tracked changes are finished, when the user asks whether work passes, before a commit, and before reporting a task done. Stays dormant in repositories with no detectable check chain, during read-only audits, and for…
agent-teams
Claude Code Agent Teams - default team-based development with strict TDD pipeline enforcement.
base
Universal coding patterns, constraints, TDD workflow, atomic todos.