timex-agent

timex-agent is a skill for Claude Code, Codex from nealpro/timex. It costs 77 tokens per session (689 once invoked), scanned A, original, MIT.

A connection between the coding agent and Timex, a local app for organising projects, tasks, work periods, and timers.

In plain words
What is it for?
Use it to inspect Timex projects and timers, plan a day, schedule focused work, and apply an approved schedule.
Why use it?
It helps turn a list of tasks into scheduled, time-limited work blocks while keeping the agent's implementation work separate from the user's plan.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/nealpro/timex/timex-agent
Any agent
npx skills add nealpro/timex --skill timex-agent
Clone the repo
git clone --depth 1 https://github.com/nealpro/timex

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for timex-agent

README.md
[![agentmods](https://agentmods.dev/badge/skills/nealpro/timex/timex-agent.svg)](https://agentmods.dev/skills/nealpro/timex/timex-agent)
Your own site
<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>
Per session 77 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 689 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 3d ago against content hash 4a5ccae88653, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

skills/timex-agent/SKILL.md · 51 lines

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-mcp from the Timex repository.
  • Build the standalone MCP/store package with zig build mcp.
  • Set TIMEX_DB_PATH=/path/to/timex.sqlite only for a test or non-default store.
  • Read timex://state-summary before proposing or making changes. Read timex://current-view when the selected project matters.

Plan Mode

  1. Inspect Timex state read-only.
  2. Identify tasks the user will perform. Exclude the coding agent's implementation, testing, or tool-use steps.
  3. Propose a schedule containing project, local start time, estimated duration, short label, and concise outcome-oriented details for every task.
  4. Ask for missing availability. Resolve ambiguous dates, times, and timezones before proposing exact calendar starts.
  5. Propose a new project when no existing project fits.
  6. 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.

  1. Re-read timex://state-summary immediately before writing.
  2. Match existing projects and timers by project, label, duration, details, and planned start; avoid duplicates.
  3. Create a proposed project only when no suitable project exists.
  4. Create each timer with duration, optional details, and optional scheduled_start.
  5. Keep scheduled timers paused. Timex starts them while the app is open when their start arrives and no timer is running.
  6. Do not start the first timer unless the approved schedule explicitly begins now. For “start now,” create an unscheduled timer, then call timer_start explicitly.
  7. Re-read state and report the created or reused project and timer IDs.

Semantic Tools

  • project_create, project_select
  • timer_create with required project_id, label, and duration
  • timer_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.

Read the full file on GitHub · 51 lines

Files

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.

Changes

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.

  1. 3d ago First seen · 51 lines · 77 tokens per session scan A 4a5ccae88653

Subscribe to this mod's changes

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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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.

obra/superpowers · 37 tokens

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.

microsoft/vscode · 62 tokens

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.

microsoft/vscode · 51 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens