Borrowing it
Nothing to install: this file belongs to optave/ops-codegraph-tool. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/optave/ops-codegraph-tool/main/.claude/skills/bench-check/SKILL.mdgit clone --depth 1 https://github.com/optave/ops-codegraph-toolWrote 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/optave/ops-codegraph-tool/bench-check)<a href="https://agentmods.dev/skills/optave/ops-codegraph-tool/bench-check"><img src="https://agentmods.dev/badge/skills/optave/ops-codegraph-tool/bench-check/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/optave/ops-codegraph-tool/bench-check"><img src="https://agentmods.dev/badge/skills/optave/ops-codegraph-tool/bench-check.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00025 | $0.02955 |
| Opus 5.5 | $0.00010 | $0.01182 |
| Sonnet 5.5 | $0.00005 | $0.00591 |
| Haiku 4.5 | $0.00003 | $0.00296 |
Grade A, and why
bench-check 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 2mo 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 — 298 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/bench-check — Performance Regression Check
Run the project's benchmark suite, compare results against a saved baseline, flag regressions beyond a threshold, and optionally update the baseline. Prevents silent performance degradation between releases.
Arguments
$ARGUMENTSmay contain:--save-baseline— run benchmarks and save as the new baseline (no comparison)--compare-only— compare against baseline without updating it--threshold N— regression threshold percentage (default: 15%)- No arguments — compare against baseline, then update it if no regressions
Phase 0 — Pre-flight
- Confirm we're in the codegraph repo root
- Check that benchmark scripts exist:
scripts/benchmark.js(build speed, query latency)scripts/incremental-benchmark.js(incremental build tiers)scripts/query-benchmark.js(query depth scaling)scripts/embedding-benchmark.js(search recall) — optional, skip if embedding deps missing
- Parse
$ARGUMENTS:SAVE_ONLY=trueif--save-baselineCOMPARE_ONLY=trueif--compare-onlyTHRESHOLD=Nfrom--threshold N(default: 15)
- Check for existing baseline at
generated/bench-check/baseline.json- If missing and not
--save-baseline: warn that this will be an initial baseline run
- If missing and not
Phase 1 — Run Benchmarks
Run each benchmark script and collect results. Each script outputs JSON to stdout.
1a. Build & Query Benchmark
output=$(timeout 300 node scripts/benchmark.js 2>&1)
exit_code=$?
If exit_code is 124: record "timeout" for this suite and skip to the next suite.
Else if exit_code is non-zero: record "error: $output" for this suite and skip to the next suite.
Extract:
buildTime(ms) — per engine (native, WASM)queryTime(ms) — per query typenodeCount,edgeCount— graph size
1b. Incremental Benchmark
output=$(timeout 300 node scripts/incremental-benchmark.js 2>&1)
exit_code=$?
If exit_code is 124: record "timeout" for this suite and skip to the next suite.
Else if exit_code is non-zero: record "error: $output" for this suite and skip to the next suite.
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.
- 2mo ago First seen · 298 lines · 25 tokens per session scan A 8b3ffe67208e
bench-check is a skill published in the GitHub repository optave/ops-codegraph-tool (99 stars, last pushed 5d ago), licensed Apache-2.0. It adds 25 tokens to every session and 2,955 once invoked, about $0.0001 per session on Opus 5.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
ix
Answer structural questions about a codebase — what a symbol is, what calls it, what a change breaks, where the hotspots are — from a persistent code graph via the ix CLI, instead of grepping.
roam
Codebase comprehension via roam-code CLI. Use when exploring codebases, planning modifications, debugging failures, assessing PR risk, or checking architecture health. Triggers on: understanding project structure, pre-change safety checks, finding symbols/files, blast radius analysis, affected tests, health scoring…
cymbal
Tree-sitter indexed code navigator. Use the cymbal CLI — not Read, Grep, Glob, or Bash — for finding where symbols are defined, tracing callers and callees, locating interface implementations, understanding the impact of a change, and mapping imports across an existing codebase. Returns precise, token-efficient…
rust-doctor
Use when Rust code just changed and must not regress, when the user asks to scan, audit or health-check a Cargo workspace, says "rust-doctor", or wants one of its findings explained, tuned or switched off.
codespaces
Build and query architecture-aware code search, dependency graphs, call flows, impact analysis, and belief maps for Python, TypeScript, TSX, Rust, C#, Java, Go, Ruby, and Ruby on Rails repositories. Use before non-trivial code changes to find module boundaries, blast radius, architecture violations, and the minimal…
review
The definitive code review, for any codebase. Five-phase workflow: git context detection (worktree, branch, base, changed files), Pharaoh recon (architecture map, module context, blast radius in one call, with a fallback when the repo isn't mapped), parallel specialized agent dispatch (code quality, security against…