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 skills add CODE-SAURABH/OpenSkills --skill benchmarkgit clone --depth 1 https://github.com/CODE-SAURABH/OpenSkillsWrote 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/code-saurabh/openskills/benchmark)<a href="https://agentmods.dev/skills/code-saurabh/openskills/benchmark"><img src="https://agentmods.dev/badge/skills/code-saurabh/openskills/benchmark/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/code-saurabh/openskills/benchmark"><img src="https://agentmods.dev/badge/skills/code-saurabh/openskills/benchmark.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00062 | $0.02976 |
| Opus 5.5 | $0.00025 | $0.01190 |
| Sonnet 5.5 | $0.00012 | $0.00595 |
| Haiku 4.5 | $0.00006 | $0.00298 |
Grade A, and why
benchmark scanned grade A with 1 finding 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 1mo 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
### Quick curl timing How it starts
The opening of the file, as written. The whole thing — 334 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Benchmark
Benchmarking without a baseline is noise. A benchmark that can't be reproduced is a guess. Every benchmark in this skill produces a number, a method, and a comparison — not an impression.
Performance is a feature. Regressions ship silently. This skill makes regressions visible before they reach users.
Benchmark Principles
- Measure before you optimize. An optimization without a before measurement is an assumption. Always baseline first.
- Reproduce exactly. A benchmark is only valid if another engineer can reproduce it with the same setup. Document the environment, the command, and the conditions.
- Medians lie. Use percentiles. P50 hides the users who are suffering. Always report P75, P95, and P99 alongside the median.
- Synthetic vs real-user data. Lighthouse in a lab tells you what's possible. RUM (Real User Monitoring) tells you what's happening. Use both.
- One change at a time. If two things change between benchmarks, you can't attribute the delta to either.
- A regression is a regression. A 10% slowdown on a fast page is still a regression. Set thresholds and enforce them.
Step 0: Establish the Baseline
Before any optimization or PR review, establish the baseline. Without it, "after" numbers are meaningless.
# Run Lighthouse baseline (3 runs, take median)
npx lighthouse https://your-app.com/key-page \
--output json \
--output-path ./baseline.json \
--chrome-flags="--headless" \
--throttling-method=simulate \
--preset=desktop
# Run 3 times and average — single runs are noisy
for i in 1 2 3; do
npx lighthouse https://your-app.com/key-page \
--output json \
--output-path "./baseline-run-$i.json" \
--chrome-flags="--headless"
done
Record in benchmark-baseline.md:
## Baseline — [Page/Endpoint] — [Date] — [Commit SHA]
| Metric | Run 1 | Run 2 | Run 3 | Median |
|--------|-------|-------|-------|--------|
| LCP | | | | |
| INP | | | | |
| CLS | | | | |
| FCP | | | | |
| TTFB | | | | |
| Total JS bundle | | | | |
| Total CSS bundle | | | | |
| Network requests | | | | |
**Environment:** macOS M2 / 6-core CPU throttle / Fast 3G simulation
**Tool:** Lighthouse 12.x / Chrome 124
**URL:** https://your-app.com/key-page
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.
- 1mo ago First seen · 334 lines · 62 tokens per session scan A 315c24f3990e
benchmark is a skill published in the GitHub repository CODE-SAURABH/OpenSkills (3 stars, last pushed 2mo ago), licensed MIT. It adds 62 tokens to every session and 2,976 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
synthetic-monitoring
AI-powered synthetic monitoring skill for e-commerce websites. Designs automated user journey tests for add-to-cart, checkout, and payment flows with alerting rules and performance baselines.
visual-regression-testing
AI-powered visual regression testing skill for e-commerce websites. Designs screenshot comparison workflows, mobile/desktop visual checks, and change detection alerts to prevent conversion-killing UI bugs.
cloudflare-workers-testing
Comprehensive testing guide for Cloudflare Workers using Vitest and @cloudflare/vitest-pool-workers. Use for test setup, binding mocks (D1/KV/R2/DO), integration tests, or encountering test failures, mock errors, coverage issues.
shopify-ab-testing
Run data-driven A/B tests on your Shopify store. Test product pages, pricing, images, copy, checkout flow, and marketing campaigns with proper statistical methodology.
api-testing
HTTP API testing for TypeScript (Supertest) and Python (httpx, pytest). Test REST APIs, GraphQL, request/response validation, authentication, and error handling.
bun-jest-migration
Use when migrating from Jest to Bun's test runner, import compatibility, mocks, and config.