time-lens

time-lens is a skill for Codex from vladmdgolam/agent-skills. It costs 108 tokens per session (6,926 once invoked), scanned A, original, MIT.

A project time tracker that combines coding, commit, and AI-assistant activity from WakaTime, Git, Claude Code, Codex CLI, and Cursor. It produces an interactive web dashboard and a Markdown report.

In plain words
What is it for?
Use it to measure time spent across one or more Git repositories, review activity by date, and create HTML and Markdown project reports.
Why use it?
It brings activity from separate tools into one view, so you can compare logged coding time with commits and assistant use instead of checking each source separately.

Skill for Codex

Written for Codex: reads ~/.codex or $CODEX_HOME. Also seen: reads .claude/ paths; mentions Claude Code; mentions Codex.

Not installable: its command points at a path on the author’s own machine, so it runs nowhere else. The line is /Users/alice/code/api-server.

Good fit Use it to measure time spent across one or more Git repositories, review activity by date, and create HTML and Markdown project reports.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.

Made for: 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 time-lens

README.md
[![agentmods](https://agentmods.dev/badge/skills/vladmdgolam/agent-skills/time-lens/github.svg)](https://agentmods.dev/skills/vladmdgolam/agent-skills/time-lens)
Your own site
<a href="https://agentmods.dev/skills/vladmdgolam/agent-skills/time-lens"><img src="https://agentmods.dev/badge/skills/vladmdgolam/agent-skills/time-lens/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.

agentmods 80×15 button for time-lens

Your own site · 80×15
<a href="https://agentmods.dev/skills/vladmdgolam/agent-skills/time-lens"><img src="https://agentmods.dev/badge/skills/vladmdgolam/agent-skills/time-lens.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 108 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 6,926 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00108 $0.06926
Opus 5 $0.00054 $0.03463
Sonnet 5 $0.00022 $0.01385
Haiku 4.5 $0.00011 $0.00693

Measured 7d ago against content hash 47e9f574e120, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

time-lens 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 7d ago.

The scan reads SKILL.md. This mod also ships 6 executable files (scripts/claude_messages.py, scripts/codex_messages.py, scripts/cursor_messages.py, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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/time-lens/SKILL.md · 404 lines

How it starts

The opening of the file, as written. The whole thing — 404 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Project Time Tracker

Combines five data sources → reconciles → produces HTML dashboard + Markdown report.

Scripts

All scripts live in scripts/ next to this SKILL.md. Run them with python3:

Script Purpose Key flags
git_sessions.py Parse git history → sessions → hours <repo> --since YYYY-MM-DD --until YYYY-MM-DD [--raw]
wakatime_fetch.py WakaTime API → daily hours, filtered to project --start YYYY-MM-DD --end YYYY-MM-DD --project name
claude_messages.py Claude Code user prompts + activity timestamps per day --project-path /abs/path or --filter name
codex_messages.py Codex CLI user prompts + activity timestamps per day --project-path /abs/path or --filter name
cursor_messages.py Cursor IDE user prompts + activity timestamps per day --project-path /abs/path or --filter name
reconcile.py Merges the JSON output of the scripts above into a single hour estimate, with an optional supervised-vs-unattended split --git f.json --claude f.json --codex f.json --since Y-M-D --until Y-M-D [--gap-hours 0.5] [--presence-window-min 10] [--tz Area/City] [--daily]

claude_messages.py, codex_messages.py, and cursor_messages.py each output two timestamp arrays: timestamps (user prompts only — for prompt-count metrics) and activity_timestamps (every timestamped event, including tool-call/tool-result cycles and assistant replies — use this one for reconciliation). See "Use activity_timestamps, not timestamps" in references/reconciliation.md for why this distinction matters — using prompt-only timestamps for hour reconciliation silently drops real work time.

Use reconcile.py instead of hand-rolling the merge in Python. It's a deterministic implementation of the algorithm below — run it on the JSON files the other scripts already produced rather than re-deriving the merge/sessionize/intersect logic inline each time. Hand-rolling it live is exactly how a real bug happened once: two different gap-threshold runs (15min vs 30min "engine time") got compared against each other as if they were the same base, producing a nonsensical number. reconcile.py fixes the gap threshold and presence window as explicit flags so every run is reproducible and comparable.

Read the full file on GitHub · 404 lines

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. 7d ago Changed · +16 lines 47e9f574e120
  2. 11d ago First seen · 388 lines · 108 tokens per session scan A a6ca6f0186a7

Subscribe to this mod's changes

time-lens is a skill published in the GitHub repository vladmdgolam/agent-skills (8 stars, last pushed 3d ago), licensed MIT. It adds 108 tokens to every session and 6,926 once invoked, about $0.0005 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.