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/whieet/harness-kit/evaluatenpx skills add whieet/harness-kit --skill evaluategit clone --depth 1 https://github.com/whieet/harness-kitWhat 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.00039 | $0.00419 |
| Opus 5 | $0.00019 | $0.00210 |
| Sonnet 5 | $0.00008 | $0.00084 |
| Haiku 4.5 | $0.00004 | $0.00042 |
Grade A, and why
evaluate 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
/harness-kit:evaluate
Run an INDEPENDENT evaluation of the current change — the robust path for Generator/Evaluator separation (a generator grading itself is unreliable).
Steps
-
Read
.harness/config.jsonfirst and follow itslanguagepreference when relaying the evaluation to the user. Do not translate file/directory names, command names, or config keys. -
Dispatch the
evaluatorsubagent (via the Task/Agent tool, subagent typeevaluator). It runs with fresh context and has no edit tools, so it cannot grade its own work. Tell it what changed (the current diff scope / the active plan). -
The evaluator will: read
.harness/rubric.md+config.verificationRecipe, run each dimension's verification check (the project's MCP tools / test runners), score every dimension 1–5 (any dimension < 3 = FAIL), append its scores to.harness/state/trace.jsonl(feeds the config suggester), and return aVERDICT: PASS | WARN | FAIL. -
Relay the verdict. On
FAIL, list the must-fix items and do not declare the task done — revise and re-evaluate. OnWARN, pass but note the technical debt.
Notes
- This is the recommended, robust evaluator path. An optional experimental auto-fire variant (a
type:agentStop hook) exists inhooks/optional-auto-eval.json— it is context-only (cannot block), runs every Stop, and is off by default; see the README before enabling it. - The Stop-hook completion gate (
harness-verify+ plan DoD) remains the hard, blocking gate; the evaluator is the subjective-quality layer on top.
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 · 24 lines · 39 tokens per session scan A c4d56dddf30f
evaluate is a skill published in the GitHub repository whieet/harness-kit (5 stars, last pushed 1mo ago), licensed MIT. It adds 39 tokens to every session and 419 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-31.
Other skills, from other repositories
paperclip
Interact with the Paperclip control plane API for task coordination and governance. Use when checking assignments, updating issue status, posting comments, delegating work, managing routines, or calling Paperclip API endpoints.
omni-mcp
Connect to the OmniRoute MCP server (110 tools, 3 transports: SSE/stdio/HTTP). Covers routing, cache, compression, memory, skills, providers, and audit tools across 33 permission scopes.
add-resend
Add Resend (email) channel integration via Chat SDK.
codegen
Code generation utilities for json-render. Use when generating code from UI specs, building custom code exporters, traversing specs, or serializing props for @json-render/codegen.
agui-dotnet-sample-step
Add a GettingStarted sample Step (a Server/Client pair) to the AG-UI .NET SDK that demonstrates one protocol feature the way we want users to write it. USE FOR: adding a new samples/GettingStarted/StepNN Server+Client pair, wiring it into AGUI.slnx and the integration-test project, giving it a deterministic…
optimize-agentic-workflow
Analyze and reduce token consumption in agentic workflows — guardrail-specific entry points, measurement, and optimization techniques.