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 skills/jarroslav/agentic-os/eval-harnessnpx skills add Jarroslav/agentic-os --skill eval-harnessgit clone --depth 1 https://github.com/Jarroslav/agentic-osWrote 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/jarroslav/agentic-os/eval-harness)<a href="https://agentmods.dev/skills/jarroslav/agentic-os/eval-harness"><img src="https://agentmods.dev/badge/skills/jarroslav/agentic-os/eval-harness.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.1 | $0.00091 | $0.02096 |
| Opus 5 | $0.00046 | $0.01048 |
| Sonnet 5 | $0.00018 | $0.00419 |
| Haiku 4.5 | $0.00009 | $0.00210 |
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 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Eval Harness
Bootstrap repo-wide evaluation for skill and agent instruction files. Two layers, one spec file per target.
| Layer | Mechanism | Failure class caught | Cost profile |
|---|---|---|---|
| Contract | Code-only checks, zero LLM calls | Structural rot: missing files, edited-away instructions, oversized bodies, broken helper scripts | Cheap — safe to run on every commit |
| Judge | Candidate model executes the skill against a case prompt; judge model grades output vs assertions | Behavioral drift: skill still loads but no longer behaves as designed | Model calls — on demand or scheduled |
Both layers exist because they detect different failure classes. Route structure to code checks and behavior to the judge: never regex-grade prose, never burn a model call to confirm a file exists.
Both layers read the same spec, eval/evals.json, colocated inside each target's directory. A spec with contracts and no behavioral cases is valid. Each judge case runs N repetitions, so flakiness surfaces as a pass rate instead of a binary verdict.
eval/here is notevals/in the agentic-os marketplace repo, and the near-collision is deliberate to name rather than rename. This skill writes<target>/eval/evals.jsoninto your repo. The marketplace repo's own CI (tests/lib/check-skill-contract.py) separately requires<skill>/evals/evals.jsonfor the skills it ships. Different scope, different owner, no conflict — except when you point this skill at the marketplace repo itself, where you will end up with both. In that one case keep the plugin'sevals/as the shipped contract and treat the generatedeval/as local scaffolding.
Blast radius: R2 — this skill writes harness code, spec files, and config into the repo. Judge runs place outbound model calls; automation wiring is opt-in and confirmed first. It never creates real credential files and never gates merges on paid model runs.
Inputs
Collect during the interview phase. Ask only what the repo has not already answered; confirm inferences rather than re-asking.
What ships with it
18 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.
- assets/ci/hooks/pre-commit 1.2 KB
- assets/python/evals.example.json 1.8 KB
- assets/python/llm_eval_runner.py 31 KB runs code
- assets/python/runner.py 17 KB runs code
- assets/python/test_runner.py 14 KB runs code
- assets/typescript/evals.example.json 2.2 KB
- assets/typescript/llm_eval_runner.mts 33 KB
- assets/typescript/runner.test.ts 18 KB runs code
- assets/typescript/runner.ts 23 KB runs code
- assets/typescript/skill-contracts.test.ts 2.0 KB runs code
- assets/typescript/tsconfig.json 997 B
- evals/evals.json 7.5 KB
- README.md 3.0 KB
- references/ci.md 7.3 KB
- references/eval-spec.md 9.9 KB
- references/judge-providers.md 7.2 KB
- references/python.md 7.4 KB
- references/typescript.md 6.2 KB
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 · 128 lines · 0 tokens per session scan A 0d58f1a89cec
eval-harness is a skill published in the GitHub repository Jarroslav/agentic-os (0 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 91 tokens to every session and 2,096 once invoked, about $0.0005 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…