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 hamzaPixl/pixl-ai --skill eval-harnessgit clone --depth 1 https://github.com/hamzaPixl/pixl-aiWrote 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/hamzapixl/pixl-ai/eval-harness)<a href="https://agentmods.dev/skills/hamzapixl/pixl-ai/eval-harness"><img src="https://agentmods.dev/badge/skills/hamzapixl/pixl-ai/eval-harness/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/hamzapixl/pixl-ai/eval-harness"><img src="https://agentmods.dev/badge/skills/hamzapixl/pixl-ai/eval-harness.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00062 | $0.00927 |
| Opus 5 | $0.00031 | $0.00464 |
| Sonnet 5 | $0.00012 | $0.00185 |
| Haiku 4.5 | $0.00006 | $0.00093 |
Grade A, and why
eval-harness 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 10d 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Eval Harness
Structured evaluation framework for measuring skill, agent, and prompt quality.
Step 0: Parse Arguments
target— skill name, agent name, or path to a prompt file--k=N— number of runs per test case (default: 3)--mode—capability(can it do X?) orregression(did it break?)
Step 1: Discover Test Cases
For Skills
- Read the skill's
SKILL.mdfor expected behavior - Check for existing eval files:
skills/<name>/evals/orskills/<name>/test-cases.jsonl - If none exist, generate test cases from the skill description
For Agents
- Read the agent's
.mdfile for trigger examples and role - Extract test scenarios from
<example>blocks - Generate edge cases from role constraints
For Prompts
- Read the prompt file
- Extract expected outputs from comments or paired
.expectedfiles
Step 2: Define Evaluation Criteria
Each test case needs:
{
"input": "the prompt or task",
"criteria": [
{"name": "correctness", "type": "binary", "description": "Does it produce the right output?"},
{"name": "format", "type": "binary", "description": "Does it follow the expected format?"},
{"name": "completeness", "type": "scale_1_5", "description": "Are all required elements present?"}
],
"blockers": ["must not hallucinate file paths", "must not modify excluded files"]
}
Step 3: Run Evaluations
For each test case, run k times:
- Execute the skill/agent/prompt
- Capture the full output
- Evaluate against criteria (use a judge prompt if automated checking isn't possible)
- Record pass/fail per criterion
Step 4: Calculate Metrics
| Metric | Formula |
|---|---|
| pass@1 | % of test cases passing on first try |
| pass@k | % passing at least once in k runs |
| precision | Correct outputs / total outputs |
| recall | Required elements present / total required |
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.
- 10d ago First seen · 109 lines · 62 tokens per session scan A 62d09303e209
eval-harness is a skill published in the GitHub repository hamzaPixl/pixl-ai (2 stars, last pushed 4mo ago), licensed MIT. It adds 62 tokens to every session and 927 once invoked, about $0.0003 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-31.
Other skills, from other repositories
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
neuron-evaluation-engineer
Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.