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 commands/araneadev/claude-timestamp/timestampsgit clone --depth 1 https://github.com/AraneaDev/claude-timestampWrote 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/commands/araneadev/claude-timestamp/timestamps)<a href="https://agentmods.dev/commands/araneadev/claude-timestamp/timestamps"><img src="https://agentmods.dev/badge/commands/araneadev/claude-timestamp/timestamps.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.1 | $0.00016 | $0.05040 |
| Opus 5 | $0.00008 | $0.02520 |
| Sonnet 5 | $0.00003 | $0.01008 |
| Haiku 4.5 | $0.00002 | $0.00504 |
Grade A, and why
timestamps 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 today.
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 — 407 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Configure the claude-timestamp plugin for this user.
Settings take effect on the next message. Every hook reads the config file each time it runs, so nothing needs restarting. Say so when you report back, because people reasonably assume otherwise.
Do all of this by reading and editing files, with Read, Edit and Write. Do not use the Bash tool for any of it: not to read the settings, not to work out the time, not to check whether a program is installed, not to apply a change. There is a terminal wizard, and the last section says how to reach it, but driving it from here is slower, noisier, and needs a Bash permission the user does not otherwise have to grant.
What the user asked for
$ARGUMENTS
What to read first
-
${CLAUDE_PLUGIN_ROOT}/schema.jsonis the contract. Itskeysobject holds every setting, its default, its acceptable values and what it does. Itspresetsobject holds a handful of whole configurations, each one naming the exact set of keys it writes. Treat it as the only source of truth about what a key may hold. -
~/.claude/claude-timestamp.facts.jsonholds what you cannot work out by reading files: whether this machine has a timezone database, whether the state directory is writable, whetherjqis present, and which plugin version is installed.Facts are grouped under
clients, keyed by the Claude Code client that wrote them. Any client name Claude Code reports is kept as its own key, socli,claude-vscodeandclaude-desktopare examples rather than the whole list, andsdk-clior a name newer than this file would each appear under themselves.unknowncovers a Claude Code too old to name itself, and anything whose name is not plain letters, digits, dashes or underscores. One home directory can serve several clients at once, so read the entry for the client you are being asked about, not whichever one happens to be first. Each entry carries awritten_atin seconds since the epoch; compare it againstdate +%sto see whether it describes this session or one from weeks ago.
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.
- today Changed · +32 lines 3b35e71da051
- 5d ago First seen · 375 lines · 16 tokens per session scan A 148ce9848e7d
timestamps is a command published in the GitHub repository AraneaDev/claude-timestamp (3 stars, last pushed yesterday), licensed MIT. It adds 16 tokens to every session and 5,040 once invoked, about $0.0001 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 commands, from other repositories
tmux-project
Open (or reuse) a project workspace session — server / agent / editor.
octo-budget-mode
Switch Octopus model routing to the configured budget tier.
resume
Resume a previous session. Reads recent session logs, open tasks, and last decisions — gives Claude full context without re-explaining the project.
explore
Fast codebase exploration with Antigravity's agy CLI (Gemini 3.7 Flash, read-only). EXPERIMENTAL.
notebook-status
Check the progress of a /agy:notebook sweep (for long document sets run with --background). Reports % complete, done/pending/failed counts, elapsed time and a rough ETA, and which documents are still pending — so you can resume. Read-only, no agy.
statusline
Show the governor fleet in your Claude Code statusline. Explicit, opt-in, and chains — it never replaces an existing statusline.