idle-time-setup

A command that displays a ready-to-paste code snippet for adding idle-time information to an existing status line. A status line is the small information display shown by a coding tool or terminal.

In plain words
What is it for?
It helps add the idle-timing fragment to an existing status-line configuration.
Why use it?
It removes the need to work out the wiring code for showing idle timing in a status line.

Command

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-setup
Clone the repo
git clone --depth 1 https://github.com/clankercode/claude-inject-idle-time
Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 854 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. 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.

ModelPer sessionOnce invoked
Fable 5 $0.00016 $0.00854
Opus 5 $0.00008 $0.00427
Sonnet 5 $0.00003 $0.00171
Haiku 4.5 $0.00002 $0.00085

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

Security

Grade B, and why

idle-time-setup scanned grade B with 1 finding 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

1. Locate the user's current statusline configuration. Read `~/.claude/settings.json` (may not exist; may be named `settings.local.json`; project-scoped settings may be at `.claude/settings.json` in the working directory
commands/idle-time-setup.md · 61 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

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.

  1. yesterday First seen · 61 lines · 16 tokens per session scan B d8607111fd06

Subscribe to this mod's changes

idle-time-setup 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 16 tokens to every session and 854 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.