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 OXI-717/ai-native-toolkit --skill agent-timegit clone --depth 1 https://github.com/OXI-717/ai-native-toolkitWrote 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/oxi-717/ai-native-toolkit/agent-time)<a href="https://agentmods.dev/skills/oxi-717/ai-native-toolkit/agent-time"><img src="https://agentmods.dev/badge/skills/oxi-717/ai-native-toolkit/agent-time/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/oxi-717/ai-native-toolkit/agent-time"><img src="https://agentmods.dev/badge/skills/oxi-717/ai-native-toolkit/agent-time.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.00018 | $0.00735 |
| Opus 5.5 | $0.00007 | $0.00294 |
| Sonnet 5.5 | $0.00004 | $0.00147 |
| Haiku 4.5 | $0.00002 | $0.00073 |
Grade A, and why
agent-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 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 — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent time
Use aw-agent-time for local time tracking and reports. This plugin supplies agent instructions; the tracker, dependencies, configuration schema, and installation scripts live in that separate repository.
Establish the installed interface
Locate the user's tracker checkout and read its README before running commands. Check the installed revision and the relevant script's --help; follow that revision's configuration and installation instructions. Do not invent a packaged CLI, flags, config keys, paths, or launchd labels. If the repository or requested capability is unavailable, state that limitation rather than substituting a private checkout or guessing an interface.
For a new installation, read the public README and inspect its installer first. Follow the user's authorized installation scope. Configure local category rules and paths from the user's environment and the documented example configuration. Keep personal mappings outside the public checkout's tracked files. Installing this plugin alone does not install ActivityWatch, watchers, or the tracker.
Report time correctly
Establish the requested date range and timezone. Check the installed tracker's day boundary; if it uses UTC, label that explicitly and do not silently describe a UTC day as a local calendar day.
Keep three measures separate:
| Layer | Meaning | Interpretation |
|---|---|---|
| 1 | Physical work | Active computer time attributed from observed activity |
| 2 | AI engagement | Interaction with AI sessions according to the tracker's engagement rules |
| 2.5 | Autonomous agent work | Agent execution recorded by the tracker, possibly concurrent |
These measures overlap. Never sum them into total human working hours. Concurrent agent time can exceed elapsed wall time; do not infer productivity gains or hours saved without a defined comparison. State source coverage, missing watchers, unmapped projects, stale data, and whether the current day is partial.
What ships with it
1 file 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.
- 20d ago Changed · -9 tokens per session 8a8f2930e92a
- 24d ago Changed 54ef0e6277b3
- 29d ago First seen · 44 lines · 27 tokens per session scan A feb58e061c52
agent-time is a skill published in the GitHub repository OXI-717/ai-native-toolkit (9 stars, last pushed 11d ago), licensed MIT. It adds 18 tokens to every session and 735 once invoked, about $0.0001 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-09-19.
Other skills, from other repositories
autoreview
Structured code review through the shared OpenClaw agent-skills installation.
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
asplos-writing-style
Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…
explore-unknowns
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…