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/openclaw/shellbench/shellbench-research-runbooknpx skills add openclaw/shellbench --skill shellbench-research-runbookgit clone --depth 1 https://github.com/openclaw/shellbenchWhat 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.00076 | $0.01124 |
| Opus 5 | $0.00038 | $0.00562 |
| Sonnet 5 | $0.00015 | $0.00225 |
| Haiku 4.5 | $0.00008 | $0.00112 |
Grade A, and why
shellbench-research-runbook 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ShellBench Research Runbook
Use this skill for a real benchmark campaign, not a one-off local score.
Read references/runbook.md before provisioning machines. It is the normative campaign contract and contains the commands, gates, artifact schema, and recovery rules.
Non-negotiable gates
- Use remote Crabbox AWS beasts for benchmark execution. Never run scored trials on the operator laptop.
- Pin one public-task commit, runner commit or patch hash, provider model ID, harness version, reasoning level, and judge route for the whole campaign.
- Run one
r0qualification for every distinct harness and model-family route, using exactly ten pinned representative tasks. Do not start full-suite jobs until model identity, real traces, tools, usage, judge routing, and artifact export pass. - Retain and audit every
r0, but force it out of leaderboard scoring. Qualify with independent full-suite repetitionsr1throughr3. After a clean audit, addr4throughr6; the research result is six total repetitions. - Run every provider-supported non-maximum reasoning level. Never label a reasoning level as tested unless the route applies it and the trace or proxy evidence proves it. Record unsupported levels instead of fabricating them.
- Use
gpt-5.6-solathighas the default judge. Keep the judge alias, credentials, logs, and identity audit separate from the agent route. - Start checkpointing after the first completed trial and continue at least every ten minutes or ten new results. Verify each local archive before it counts.
- Upload every verified checkpoint and final archive to the private S3 prefix
from
SHELLBENCH_TRACE_S3_URI. Never put bucket names or credentials in git, PR text, public logs, or generated reports. - A run is not research-clean when traces are missing, observed model identity differs from the request, reasoning is unproven, coverage is incomplete, or infrastructure failures dominate.
What ships with it
2 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.
- 3d ago First seen · 111 lines · 76 tokens per session scan A 7c327fcaaae0
shellbench-research-runbook is a skill published in the GitHub repository openclaw/shellbench (138 stars, last pushed 5d ago), licensed MIT. It adds 76 tokens to every session and 1,124 once invoked, about $0.0004 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…