timing-benchmark

timing-benchmark is a command for coding agents from oghie/skillsets. It costs 0 tokens per session (158 once invoked), scanned A, original, MIT.

A benchmarking procedure for measuring how long software takes to respond, how much that time varies, and how often it misses deadlines. It reports both typical results and slow tail results such as p95, p99, and maximum latency.

In plain words
What is it for?
Use it to benchmark latency, jitter, response times, deadline misses, and performance changes under CPU, memory, storage, or network load.
Why use it?
It prevents averages from hiding rare but important delays. It also records the machine, operating system, runtime, compiler settings, workload, and background load so results can be compared fairly.

Command

Part of the skillsets plugin — 9 skills, 4 commands, 1 hook, 4 MCP servers shipped together

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.

agentmods
npx agentmods add commands/oghie/skillsets/timing-benchmark
Clone the repo
git clone --depth 1 https://github.com/oghie/skillsets

Or install skillsets, the plugin that ships this one along with the rest of its 9 skills, 4 commands, 1 hook, 4 MCP servers.

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 timing-benchmark

README.md
[![agentmods](https://agentmods.dev/badge/commands/oghie/skillsets/timing-benchmark.svg)](https://agentmods.dev/commands/oghie/skillsets/timing-benchmark)
Your own site
<a href="https://agentmods.dev/commands/oghie/skillsets/timing-benchmark"><img src="https://agentmods.dev/badge/commands/oghie/skillsets/timing-benchmark.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 158 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found 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 $0.00000 $0.00158
Opus 5 $0.00000 $0.00079
Sonnet 5 $0.00000 $0.00032
Haiku 4.5 $0.00000 $0.00016

Measured 5d ago against content hash e2d80de11275, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

skills/realtime-systems-coding/commands/timing-benchmark.md · 20 lines

What it actually says

Timing Benchmark Command

Goal

Measure latency, jitter, and deadline behavior without hiding tail risk behind averages.

Procedure

  1. Pin environment: CPU, clock source, OS/kernel, container/VM limits, compiler flags, runtime version, and load.
  2. Warm up runtime where needed.
  3. Capture release time, start time, finish time, response time, and deadline miss count.
  4. Report min, p50, p95, p99, max, and missed deadlines.
  5. Repeat under background CPU, memory, I/O, and network load as appropriate.
  6. Compare against baseline and include raw command lines.

Output

  • Environment.
  • Workload.
  • Timing distribution.
  • Deadline miss count.
  • Interpretation tied to the original timing requirement.
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. 5d ago First seen · 20 lines · 0 tokens per session scan A e2d80de11275

Subscribe to this mod's changes

timing-benchmark is a command published in the GitHub repository oghie/skillsets (9 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 158 tokens. 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-31.