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/mifunedev/openharness/benchmarknpx skills add mifunedev/openharness --skill benchmarkgit clone --depth 1 https://github.com/mifunedev/openharnessWhat 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.00212 | $0.02030 |
| Opus 5 | $0.00106 | $0.01015 |
| Sonnet 5 | $0.00042 | $0.00406 |
| Haiku 4.5 | $0.00021 | $0.00203 |
Grade A, and why
benchmark 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 3d 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Benchmark — progress-ceiling verdict gate
The benchmark gate, part of /spec execute's improve tail in
.oh/skills/spec/SKILL.md. It answers one question: was this change actually beneficial — did it
move or hold the capability ceiling without breaking the regression floor, and is
it worth its complexity? — and emits exactly one verdict.
Core principle: compose, don't re-derive — and judge OUTCOMES, not machinery.
This skill owns the verdict, not the instruments. The regression floor is
/eval; the progress ceiling is the capability benchmark (.oh/evals/capability/).
/benchmark runs both and integrates them into a single BENEFICIAL /
NOT-BENEFICIAL. Adding machinery is not progress — a change
that grows the harness but does not move the capability benchmark is
NOT-BENEFICIAL by definition.
Not
/audit implementation./audit implementationis the per-unit floor gate (does this one impl satisfy its task graph and is it promotable?)./benchmarkis the ceiling gate (did the harness get better?). Distinct instruments, distinct question — see.oh/evals/capability/README.md§ Ceiling vs. floor./benchmarkconsults/eval; it does not replace or fork it.
Inputs
| Arg | Meaning |
|---|---|
--base <ref> |
The counterfactual to score against — the state without this change. Defaults to the merge-base with development (i.e. "the repo before this change"). |
--cycles <N> |
Window for the redirect signal (§ Redirect signal). Default 3: a benchmark flat for N consecutive cycles while machinery grows trips the human-redirect flag. |
The two signals (fail-fast, in order)
Run in order; the first signal that decides NOT-BENEFICIAL ends the gate.
Only when both signals clear is the verdict BENEFICIAL. A signal that is
missing or ambiguous is treated as NOT-BENEFICIAL, never as beneficial
(honest exits).
Signal 1 — Regression floor (/eval)
A change that breaks the floor is never beneficial, whatever it claims to add. Gate on the runner's exit code + delta, not its prose — and read the cycle's single run rather than launching a third one:
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.
- 3d ago First seen · 165 lines · 212 tokens per session scan A 572bcfc7a05e
benchmark is a skill published in the GitHub repository mifunedev/openharness (36 stars, last pushed 3d ago), licensed Apache-2.0. It adds 212 tokens to every session and 2,030 once invoked, about $0.0011 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
data-visualization
Use for creating publication-quality charts and multi-panel analysis summaries. Triggers when tasks involve visualizing data, plotting results, creating charts, or producing visual reports from analysis output.
cuml-machine-learning
Use for GPU-accelerated machine learning on tabular data using NVIDIA cuML. Triggers when tasks involve classification, regression, clustering, dimensionality reduction, or model training on datasets.
blog-post
Writes and structures long-form blog posts, creates tutorial outlines, and optimizes content for SEO with cover image generation. Use when the user asks to write a blog post, article, how-to guide, tutorial, technical writeup, thought leadership piece, or long-form content.
social-media
Drafts engaging social media posts, writes hooks, suggests hashtags, creates thread structures, and generates companion images. Use when the user asks to write a LinkedIn post, tweet, Twitter/X thread, social media caption, social post, or repurpose content for social platforms.
remember
Review the current conversation and capture valuable knowledge — best practices, coding conventions, architecture decisions, workflows, and user feedback — into persistent memory (AGENTS.md) or reusable skills. Use when the user says: (1) remember this, (2) save what we learned, (3) update memory, (4) capture…
textual-screenshot
Capture a Textual terminal UI as an SVG using its headless test harness. Use when asked to make, attach, or preview a screenshot of deepagents-code/dcode or another Textual app, visually verify a TUI state, or render a modal, screen, or widget without a desktop or browser.