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/jetxu-llm/docmason/operator-evalnpx skills add JetXu-LLM/DocMason --skill operator-evalgit clone --depth 1 https://github.com/JetXu-LLM/DocMasonWrote 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/jetxu-llm/docmason/operator-eval)<a href="https://agentmods.dev/skills/jetxu-llm/docmason/operator-eval"><img src="https://agentmods.dev/badge/skills/jetxu-llm/docmason/operator-eval.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 | $0.00027 | $0.00345 |
| Opus 5 | $0.00014 | $0.00172 |
| Sonnet 5 | $0.00005 | $0.00069 |
| Haiku 4.5 | $0.00003 | $0.00034 |
Grade A, and why
operator-eval 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.
What it actually says
Operator Eval
Use this workflow only for advanced operator-quality tasks such as replayable evaluation runs, regression review, candidate promotion, and baseline freezing.
This workflow is intentionally open-source but non-first-contact.
Do not surface it in ordinary user entry flows, and do not treat it as part of the default ask experience.
Required Capabilities
- local file access
- shell or command execution
- ability to inspect structured JSON output
Procedure
- Read the current operator request from
runtime/eval/requests/current.json. - Validate the request against the tracked examples in
skills/operator/operator-eval/examples/. - Execute exactly one requested action through the
operator-evalruntime surface:run-suitereview-regressionspromote-candidatefreeze-baseline
- Keep live eval truth under
runtime/eval/, not under tracked repository paths. - Keep review of ordinary runtime activity under
runtime/logs/. - Treat tracked examples as schema guidance only. Never commit confidential runtime/eval payloads.
- Return the operator-facing result, written artifacts, and next corrective step to the main agent.
Notes
- This workflow is intentionally absent from first-contact guidance.
- Frozen baselines and promotion decisions remain human-governed even though this workflow is productized.
skills/operator/operator-eval/examples/exists so fresh open-source users can understand the local-only artifact contracts without access to private corpus data.
What ships with it
7 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.
- 5d ago First seen · 38 lines · 27 tokens per session scan A 1caccec51b07
operator-eval is a skill published in the GitHub repository JetXu-LLM/DocMason (135 stars, last pushed yesterday), licensed Apache-2.0. It adds 27 tokens to every session and 345 once invoked, about $0.0001 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
openkb-deck-neon
Use when the user asks the openkb chat to make a deck / slide presentation / PPT / slides / 演示稿 / 幻灯片 from their compiled KB content AND wants a dark, high-tech, neon / glow / glassmorphism look (赛博 / 科技风 / 暗色 / 霓虹 / 炫酷). Generates a polished single-file HTML deck in the Aurora Glass visual direction (near-black…
openkb-deck-editorial
Use when the user asks the openkb chat to make a deck / slide presentation / PPT / slides / 演示稿 / 幻灯片 from their compiled KB content. Generates a polished single-file HTML deck in the Editorial Monocle visual direction (warm cream background, serif type, brick-red accent) — designed to be opened in a browser…
openkb-html-critic
Use to review a generated HTML deck or single-page artifact for visual quality and structural correctness. Especially good at catching CSS specificity bugs where slide-modifier classes (.divider, .center, .q, .flow etc.) accidentally override the base .slide{display:none} and cause one slide to stack on top of every…
transformer-attention
Use when reasoning about Transformer self-attention, multi-head attention, positional encoding, masked decoder attention, or why attention replaced recurrence/convolutions in sequence models; not for generic NLP or unrelated attention topics.
openkb
Use when the user asks about content in their OpenKB knowledge base — research topics, concepts compiled from their documents, cross-document synthesis — or mentions openkb, an .openkb/ directory, or a wiki/ tree generated by openkb. The user may invoke you from any working directory; the active KB resolves via openkb…
openlore
Query and publish to an OpenLore knowledge base over SSH using ordinary shell commands. Use when a task needs project documentation, runbooks, shared team knowledge, or a place to publish findings.