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/nealpro/timex/timex-agentnpx skills add nealpro/timex --skill timex-agentgit clone --depth 1 https://github.com/nealpro/timexWrote 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/nealpro/timex/timex-agent)<a href="https://agentmods.dev/skills/nealpro/timex/timex-agent"><img src="https://agentmods.dev/badge/skills/nealpro/timex/timex-agent.svg" alt="Measured on agentmods" 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 | $0.00077 | $0.00689 |
| Opus 5 | $0.00039 | $0.00345 |
| Sonnet 5 | $0.00015 | $0.00138 |
| Haiku 4.5 | $0.00008 | $0.00069 |
Grade A, and why
timex-agent 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 3d 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Timex Agent
Connect
- Launch
zig-out/bin/timex-mcpfrom the Timex repository. - Build the standalone MCP/store package with
zig build mcp. - Set
TIMEX_DB_PATH=/path/to/timex.sqliteonly for a test or non-default store. - Read
timex://state-summarybefore proposing or making changes. Readtimex://current-viewwhen the selected project matters.
Plan Mode
- Inspect Timex state read-only.
- Identify tasks the user will perform. Exclude the coding agent's implementation, testing, or tool-use steps.
- Propose a schedule containing project, local start time, estimated duration, short label, and concise outcome-oriented details for every task.
- Ask for missing availability. Resolve ambiguous dates, times, and timezones before proposing exact calendar starts.
- Propose a new project when no existing project fits.
- Do not create or modify projects or timers in Plan Mode.
Apply an Approved Schedule
Treat the user's approval to implement the proposed plan as authorization to create its project and paused timers before other execution work.
- Re-read
timex://state-summaryimmediately before writing. - Match existing projects and timers by project, label, duration, details, and planned start; avoid duplicates.
- Create a proposed project only when no suitable project exists.
- Create each timer with
duration, optionaldetails, and optionalscheduled_start. - Keep scheduled timers paused. Timex starts them while the app is open when their start arrives and no timer is running.
- Do not start the first timer unless the approved schedule explicitly begins now. For “start now,” create an unscheduled timer, then call
timer_startexplicitly. - Re-read state and report the created or reused project and timer IDs.
Semantic Tools
project_create,project_selecttimer_createwith requiredproject_id,label, anddurationtimer_start,timer_pause,timer_reset,timer_delete
Use durations such as 25m, 1h, or 1h 30m. Use RFC 3339 calendar starts with an explicit offset, such as 2026-07-21T15:30:00+05:30. Timex stores calendar instants in UTC and displays them in the system timezone.
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.
- 3d ago First seen · 51 lines · 77 tokens per session scan A 4a5ccae88653
timex-agent is a skill published in the GitHub repository nealpro/timex (0 stars, last pushed 1mo ago), licensed MIT. It adds 77 tokens to every session and 689 once invoked, about $0.0004 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…