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/x-cmd/x-cmd/timenpx skills add x-cmd/x-cmd --skill timegit clone --depth 1 https://github.com/x-cmd/x-cmdWhat 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.00046 | $0.00428 |
| Opus 5 | $0.00023 | $0.00214 |
| Sonnet 5 | $0.00009 | $0.00086 |
| Haiku 4.5 | $0.00005 | $0.00043 |
Grade A, and why
time 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 2d 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.
What it actually says
time — skill0
Measure command execution time. From single-shot microsecond timing to multi-run statistical analysis.
Quick Start
# With x-cmd
x time <command> # Single microsecond timing
x time stress -c 100 <command> # 100-run statistics
x time cmp 'cmd1' 'cmd2' 'cmd3' # Compare commands
# Without x-cmd — use shell built-ins
time <command> # Basic timing
# For benchmarking, use a loop:
for i in $(seq 1 100); do
start=$(date +%s%N)
<command>
end=$(date +%s%N)
echo $(( end - start ))
done
What's Available
x time <cmd>— Single run, microsecond precisionx time getms <cmd>— Millisecond precisionx time stress -c N <cmd>— N runs with full statsx time stress -b N <cmd>— Auto-decide runs within budgetx time cmp 'c1' 'c2'— Compare multiple commands
Output Formats
--csvCSV for programmatic analysis--tsvTab-separated--ymlYAML
This skill0 grows
Starting with the essentials. Will add:
- Benchmarking patterns
- Statistical interpretation guide
- Common performance anti-patterns
Related
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.
- 2d ago First seen · 63 lines · 46 tokens per session scan A 56702d1ef24e
time is a skill published in the GitHub repository x-cmd/x-cmd (4,624 stars, last pushed 4d ago), licensed Apache-2.0. It adds 46 tokens to every session and 428 once invoked, about $0.0002 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
claude-api
Build, debug, and optimize Claude API / Anthropic SDK apps. Apps built with this skill should include prompt caching. Also handles migrating existing Claude API code between Claude model versions (4.5 → 4.6, 4.6 → 4.7, retired-model replacements). TRIGGER when: code imports anthropic/@anthropic-ai/sdk; user asks for…
gui-onboarding-verification-skill
GUI desktop app only. Launch two parallel Oz cloud agents with computer use to download and install the latest stable Linux Warp build, capture screenshots while walking through first-time onboarding in both logged-out and logged-in states, then selectively fan out follow-up cloud agents for distinct onboarding…
create-skill
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
gui-integration-test
GUI desktop app only. Writes, runs, and debugs Warp integration tests using the custom Builder/TestStep framework in crates/integration. Use when adding a new integration test, fixing a failing integration test, wiring a test into the manual runner or nextest suite, or verifying end-to-end UI and terminal behavior in…
gui-settings-ui
GUI desktop app only. How to build a Settings page in the Warp client (app/src/settingsview) so its widgets and settings search behave correctly — picking a PageType, deciding whether a heading belongs in the page-title slot or inside a widget, gating a widget, and scoping searchterms per widget. Use when adding or…
logging-and-error-reporting
How and when to log (log:: levels, safe macros) and report errors to Sentry (reporterror!) in the Warp codebase. Use when adding or reviewing any logging or error reporting — picking a log level, deciding log vs. reporterror!, keeping sensitive data out of logs, or surfacing an error to Sentry.