What is idle-time-status?

A one-time self-test for an idle-timing plugin, checking its data directory, hook scripts, and logs.

Use it to check the installation and operation of the idle-timing plugin.

It helps identify whether the plugin's supporting files and recorded logs are set up correctly.

idle-time-status — Command by clankercode

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 commands/clankercode/claude-inject-idle-time/idle-time-status

Clone the repo

git clone --depth 1 https://github.com/clankercode/claude-inject-idle-time

Per session 21 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 106 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin unknown 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.

Model	Per session	Once invoked
Fable 5	$0.00021	$0.00106
Opus 5	$0.00010	$0.00053
Sonnet 5	$0.00004	$0.00021
Haiku 4.5	$0.00002	$0.00011

Measured yesterday against content hash b31dc1189f8c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

idle-time-status 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 yesterday.

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/idle-time-status.md · 17 lines

The source is not reproduced here

No licence file

Read it on GitHub

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.

yesterday First seen · 17 lines · 21 tokens per session scan A b31dc1189f8c

Subscribe to this mod's changes

idle-time-status is a command published in the GitHub repository clankercode/claude-inject-idle-time (5 stars, last pushed 2mo ago), with no licence file. It adds 21 tokens to every session and 106 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.

Languages Testing claude-code devtools javascript nodejs plugin timing

idle-time-status

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

The source is not reproduced here

No licence file

What this file has done since we first saw it

Other commands, from other repositories

shadcn-add

find-issues

find-duplicate-prs

upgrade-nodejs

upgrade-webkit

dedupe