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 easyzoom/aix-skills --skill embedded-timing-libsgit clone --depth 1 https://github.com/easyzoom/aix-skillsWrote 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/easyzoom/aix-skills/embedded-timing-libs)<a href="https://agentmods.dev/skills/easyzoom/aix-skills/embedded-timing-libs"><img src="https://agentmods.dev/badge/skills/easyzoom/aix-skills/embedded-timing-libs/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/easyzoom/aix-skills/embedded-timing-libs"><img src="https://agentmods.dev/badge/skills/easyzoom/aix-skills/embedded-timing-libs.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.00035 | $0.00538 |
| Opus 5 | $0.00017 | $0.00269 |
| Sonnet 5 | $0.00007 | $0.00108 |
| Haiku 4.5 | $0.00003 | $0.00054 |
Grade A, and why
embedded-timing-libs 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 9d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Embedded Timing Libs
Overview
Use this skill for lightweight software timer libraries such as MultiTimer. The agent should confirm tick source, callback context, time units, wraparound behavior, and scheduler frequency before relying on timer callbacks.
When To Use
Use this skill when:
- The user wants to add or debug MultiTimer, software timers, timeout lists, periodic callbacks, or one-shot timers.
- Timers drift, fire too early/late, stop firing, fire repeatedly, or break across tick overflow.
Do not use this skill for hardware PWM/timer peripheral bring-up. Use embedded-peripheral-bringup for register-level timer issues.
First Questions
Ask for:
- Timer library and target runtime.
- Tick source and frequency.
- Callback context: main loop, RTOS task, ISR, or scheduler hook.
- Time units used by the library and application.
- Number of timers and longest expected uptime.
- Whether callbacks may start/stop other timers.
Integration Checklist
-
Confirm tick monotonicity. Timer logic needs a stable increasing timebase or explicit wraparound handling.
-
Match units. Milliseconds, ticks, microseconds, and RTOS ticks must not be mixed silently.
-
Define callback context. Timer callbacks must not block if they run in ISR or scheduler critical context.
-
Test one-shot and periodic behavior. Verify start, stop, restart, and callback ordering.
-
Test wraparound. Use simulated ticks or shortened counters to prove overflow behavior.
Common Failures
- Tick function returns seconds while timer expects milliseconds.
- Callback blocks in interrupt context.
- Timer list is modified while iterating without protection.
- Drift accumulates because periodic timers restart from callback time instead of scheduled time.
- Wraparound breaks after long uptime.
Verification
Before claiming timer integration works:
- State tick source, frequency, unit, callback context, and protection strategy.
- Confirm one-shot, periodic, cancel, restart, and wraparound behavior.
- Confirm callback execution time is acceptable.
- Confirm timer operations are safe from ISR/task contexts in use.
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.
- 9d ago First seen · 79 lines · 35 tokens per session scan A df9b82e8e05f
embedded-timing-libs is a skill published in the GitHub repository easyzoom/aix-skills (31 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session and 538 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
container-home
Answer questions, assist with planning, and help with design decisions for Mick's off-grid shipping container lake home project. Trigger when the user mentions the container home, lake home, Stewart County, LBL, the expansion, solar system, septic permitting, or retirement property.
eide
A build tool for EIDE projects, an embedded-development extension for Visual Studio Code. It finds EIDE project settings and builds firmware using ARM CC or GCC.
audit
Project health audit and health check — architecture, performance, tests, dependencies, code quality. Use when assessing overall project health, before releases, or after refactors.
workflow
A workflow skill for embedded-device projects that plans and runs building, flashing, debugging, observing, and diagnosis tasks.
investigate
Investigate bugs and errors in Elixir/Phoenix — root-cause analysis for crashes, exceptions, stack traces, test failures. Use --parallel for deep 4-track investigation.
narrow-bare-rescue
Narrow bare rescue in Elixir so real errors like KeyError and typos propagate instead of being swallowed. Use to audit rescues and refactor error handling.