chronos-when

chronos-when is a command for Claude Code from OthmanAdi/chronos. It costs 26 tokens per session (152 once invoked), scanned A, original, MIT.

A command that searches recent coding sessions and reports when a command, file edit, or search last ran. It includes the local time, elapsed time, result, and duration when a match is found.

In plain words
What is it for?
It helps decide whether to rerun a command, edit, or search by finding its most recent recorded execution.
Why use it?
It removes the need to guess whether an action already happened or search through session history by hand.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter.

Part of the chronos plugin — 1 skill, 4 commands, 3 hooks shipped together

Good fit It helps decide whether to rerun a command, edit, or search by finding its most recent recorded execution.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/othmanadi/chronos/chronos-when
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.

Clone the repo
git clone --depth 1 https://github.com/OthmanAdi/chronos

Made for: Claude Code.

Or install chronos, the plugin that ships this one along with the rest of its 1 skill, 4 commands, 3 hooks.

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 chronos-when

README.md
[![agentmods](https://agentmods.dev/badge/commands/othmanadi/chronos/chronos-when/github.svg)](https://agentmods.dev/commands/othmanadi/chronos/chronos-when)
Your own site
<a href="https://agentmods.dev/commands/othmanadi/chronos/chronos-when"><img src="https://agentmods.dev/badge/commands/othmanadi/chronos/chronos-when/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 chronos-when

Your own site · 80×15
<a href="https://agentmods.dev/commands/othmanadi/chronos/chronos-when"><img src="https://agentmods.dev/badge/commands/othmanadi/chronos/chronos-when.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 26 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 152 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.00026 $0.00152
Opus 5.5 $0.00010 $0.00061
Sonnet 5.5 $0.00005 $0.00030
Haiku 4.5 $0.00003 $0.00015

Measured 1mo ago against content hash e2fbebf0a27e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

chronos-when 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 1mo 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.

commands/chronos-when.md · 16 lines

What it actually says

Run chronos when $ARGUMENTS, which searches recent sessions for tool calls whose name or target matches the text, newest first.

Show the results. Each row carries how long ago it was, the local time, whether it succeeded, and how long it took.

If nothing matches, widen the search with --days 30 before reporting that there is no record. If the user was asking in order to decide whether to re-run something, answer that question directly using the timestamp rather than making them read the table.

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. 1mo ago First seen · 16 lines · 26 tokens per session scan A e2fbebf0a27e

Subscribe to this mod's changes

chronos-when is a command published in the GitHub repository OthmanAdi/chronos (3 stars, last pushed 1mo ago), licensed MIT. It adds 26 tokens to every session and 152 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-05.