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 sfc-gh-myoung/ai_coding_rules --skill skill-timergit clone --depth 1 https://github.com/sfc-gh-myoung/ai_coding_rulesWrote 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/sfc-gh-myoung/ai_coding_rules/skill-timer)<a href="https://agentmods.dev/skills/sfc-gh-myoung/ai_coding_rules/skill-timer"><img src="https://agentmods.dev/badge/skills/sfc-gh-myoung/ai_coding_rules/skill-timer/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/sfc-gh-myoung/ai_coding_rules/skill-timer"><img src="https://agentmods.dev/badge/skills/sfc-gh-myoung/ai_coding_rules/skill-timer.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.00074 | $0.02457 |
| Opus 5.5 | $0.00030 | $0.00983 |
| Sonnet 5.5 | $0.00015 | $0.00491 |
| Haiku 4.5 | $0.00007 | $0.00246 |
Grade A, and why
skill-timer 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 20d 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 — 245 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Timer
Timing instrumentation for skill execution measurement with microsecond precision and anomaly detection.
Purpose
Enable comprehensive performance measurement and analysis:
- Wall-clock duration: microsecond precision from start to end.
- Checkpoints: intermediate timing points for bottleneck analysis.
- Token tracking: input/output token counts with cost estimation.
- Anomaly detection: real-time detection of shortcuts and timeouts.
- Baseline comparison: compare against historical averages.
- Cross-analysis: performance across models, agents, and modes.
Use this skill when
- Measuring skill execution duration.
- Comparing performance across models or agents.
- Identifying bottlenecks with checkpoints.
- Tracking token consumption and costs.
- Detecting potential agent shortcuts (suspiciously fast execution).
- Building performance baselines for CI/CD.
- Analyzing historical timing trends.
Do not use for: skills with sub-5-second expected duration, pure syntax tests, or skills that produce no file output (timing metadata needs a file to embed in).
Quick Start
# Measure a skill execution with checkpoints
Use the skill-timer skill.
skill_name: rule-reviewer
target_file: rules/200-python-core.md
model: claude-sonnet-4-6
review_mode: FULL
timing_enabled: true
Output: Timing metadata embedded in output file with duration, checkpoints, token costs, and baseline comparison.
Inputs
Required (timing-start)
skill_name:string: name of the skill being timed.target_file:path: target file path.model:string: model slug (e.g.,claude-sonnet-4-6).
Required (timing-end)
run_id:hex string (16 chars): from timing-start output.output_file:path: output file for metadata embedding.skill_name:string: skill name (for recovery ifrun_idlost).
Optional (timing-end)
input_tokens:integer(default: none).output_tokens:integer(default: none).format:string(default:human):human,json,markdown,quiet.dimension_timings:JSON array(default: none): per-dimension timing data.auto_dimension_timings:flag(default: off): derivedimension_timingsautomatically fromdim_<name>_start/dim_<name>_endcheckpoint pairs. Explicitdimension_timingswins if both are supplied (with WARNING).review_mode:string(default:FULL).
What ships with it
26 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.
- CHANGELOG.md 8.5 KB
- examples/baseline-workflow.md 3.9 KB
- examples/basic-timing.md 2.9 KB
- examples/ci-integration.md 6.0 KB
- examples/with-checkpoints.md 4.8 KB
- examples/with-wrap.md 2.4 KB
- pyproject.toml 165 B
- references/dimension-timings.md 1.5 KB
- references/integration-pattern.md 1.4 KB
- schemas/timing-output.schema.json 9.8 KB
- scripts/find_python.sh 1.8 KB runs code
- scripts/skill_timer.py 89 KB runs code
- scripts/validate_timing.py 3.2 KB runs code
- tests/__init__.py 33 B runs code
- tests/fixtures/run_f92f9d72f408a356.json 4.6 KB
- tests/test_per_dimension_timing.py 8.0 KB runs code
- tests/test_skill_timer.sh 21 KB runs code
- tests/test_v3_robustness.py 14 KB runs code
- uv.lock 131 B
- workflows/advanced-operations.md 2.1 KB
- workflows/timing-checkpoint.md 2.0 KB
- workflows/timing-end.md 3.8 KB
- workflows/timing-finalize.md 1.3 KB
- workflows/timing-start.md 1.5 KB
- workflows/timing-wrap.md 2.5 KB
- workflows/validation-checkpoints.md 1.9 KB
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.
- 20d ago First seen · 245 lines · 74 tokens per session scan A ffcafff9d664
skill-timer is a skill published in the GitHub repository sfc-gh-myoung/ai_coding_rules (8 stars, last pushed 2d ago), licensed Apache-2.0. It adds 74 tokens to every session and 2,457 once invoked, about $0.0003 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-10-10.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…