benchmark

benchmark is a skill for Claude Code, Codex from Jamkris/everything-gemini-code. It costs 8 tokens per session (606 once invoked), scanned A, a copy of benchmark, MIT.

A tool for measuring application performance and detecting regressions, meaning changes that make a page or API slower than before.

In plain words
What is it for?
Use it before and after code changes, before launches, or when checking page speed and API latency.
Why use it?
It replaces guesses about slowness with repeatable measurements from web pages and API requests.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it before and after code changes, before launches, or when checking page speed and API latency.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jamkris/everything-gemini-code/benchmark
Install

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.

Any agent
npx skills add Jamkris/everything-gemini-code --skill benchmark
Clone the repo
git clone --depth 1 https://github.com/Jamkris/everything-gemini-code

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for benchmark

README.md
[![agentmods](https://agentmods.dev/badge/skills/jamkris/everything-gemini-code/benchmark.svg)](https://agentmods.dev/skills/jamkris/everything-gemini-code/benchmark)
Your own site
<a href="https://agentmods.dev/skills/jamkris/everything-gemini-code/benchmark"><img src="https://agentmods.dev/badge/skills/jamkris/everything-gemini-code/benchmark.svg" alt="Measured on agentmods" height="20"></a>
Per session 8 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 606 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 75% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00008 $0.00606
Opus 5 $0.00004 $0.00303
Sonnet 5 $0.00002 $0.00121
Haiku 4.5 $0.00001 $0.00061

Measured 3d ago against content hash 11a41b377ba6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

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.

Origin

This is a copy

75% identical to benchmark — 29 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/benchmark/SKILL.md · 93 lines

How it starts

The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Benchmark — Performance Baseline & Regression Detection

When to Use

  • Before and after a PR to measure performance impact
  • Setting up performance baselines for a project
  • When users report "it feels slow"
  • Before a launch — ensure you meet performance targets
  • Comparing your stack against alternatives

How It Works

Mode 1: Page Performance

Measures real browser metrics via browser MCP:

1. Navigate to each target URL
2. Measure Core Web Vitals:
   - LCP (Largest Contentful Paint) — target < 2.5s
   - CLS (Cumulative Layout Shift) — target < 0.1
   - INP (Interaction to Next Paint) — target < 200ms
   - FCP (First Contentful Paint) — target < 1.8s
   - TTFB (Time to First Byte) — target < 800ms
3. Measure resource sizes:
   - Total page weight (target < 1MB)
   - JS bundle size (target < 200KB gzipped)
   - CSS size
   - Image weight
   - Third-party script weight
4. Count network requests
5. Check for render-blocking resources

Mode 2: API Performance

Benchmarks API endpoints:

1. Hit each endpoint 100 times
2. Measure: p50, p95, p99 latency
3. Track: response size, status codes
4. Test under load: 10 concurrent requests
5. Compare against SLA targets

Mode 3: Build Performance

Measures development feedback loop:

1. Cold build time
2. Hot reload time (HMR)
3. Test suite duration
4. TypeScript check time
5. Lint time
6. Docker build time

Mode 4: Before/After Comparison

Run before and after a change to measure impact:

/benchmark baseline    # saves current metrics
# ... make changes ...
/benchmark compare     # compares against baseline

Output:

| Metric | Before | After | Delta | Verdict |
|--------|--------|-------|-------|---------|
| LCP | 1.2s | 1.4s | +200ms | ⚠ WARN |
| Bundle | 180KB | 175KB | -5KB | ✓ BETTER |
| Build | 12s | 14s | +2s | ⚠ WARN |

Output

Stores baselines in .ecc/benchmarks/ as JSON. Git-tracked so the team shares baselines.

Integration

  • CI: run /benchmark compare on every PR
  • Pair with /canary-watch for post-deploy monitoring
  • Pair with /browser-qa for full pre-ship checklist

Read the full file on GitHub · 93 lines

Changes

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.

  1. 3d ago First seen · 93 lines · 8 tokens per session scan A 11a41b377ba6

Subscribe to this mod's changes

benchmark is a skill published in the GitHub repository Jamkris/everything-gemini-code (87 stars, last pushed 3mo ago), licensed MIT. It adds 8 tokens to every session and 606 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 75% identical to benchmark, differing in 29 lines, and is treated as a copy.

Related

Other skills, from other repositories

debugging

MUST USE for any real runtime debugging across ANY language or binary — crashes, silent failures, wrong responses, stuck processes, memory leaks, async misbehavior, unexplained timing, reverse engineering. Runs a hypothesis-driven loop: form ≥3 hypotheses, investigate in parallel, after 2 failed rounds spawn Oracles…

daeryundf2-prog/LAZYANTIGRAVITY · 244 tokens

report-bug

Create a high-signal bug issue or PR in the repo that owns the defect. Use this whenever the user asks to report, file, open, or triage a LazyAntigravity plugin, bundled component, skill, hook, MCP, installer, or packaging bug, especially when they need source-backed root cause, reproduction steps, fix guidance, and…

daeryundf2-prog/LAZYANTIGRAVITY · 79 tokens

debug-assistant

Systematic debugging assistant that helps identify and fix bugs through structured analysis, hypothesis testing, and root cause identification. Use when facing errors, unexpected behavior, or mysterious bugs.

richardcb/oh-my-gemini · 39 tokens

quick-fix

Apply a minimal, targeted fix to a specific bug or issue. Focused on speed and precision - locate the problem, make the smallest correct change, and verify. Not a planning workflow; use for small fixes, patches, and hotfixes.

richardcb/oh-my-gemini · 55 tokens

lcx-report-bug

Alias for report-bug. Create a high-signal bug issue or PR in the repo that owns the defect.

daeryundf2-prog/LAZYANTIGRAVITY · 29 tokens

bug-fixing

Group skill: Systematic bug fixing — diagnose, error analysis, trace logs, performance profiling, targeted fix, regression test, code review, and postmortem.

may215/antigravity-awesome-group-skills · 37 tokens