agentmods.dev

timeline-setup

timeline-setup is a command for Claude Code from BlazeMV/blaze-claude-plugins. It costs 27 tokens per session (238 once invoked), scanned B, original, MIT.

A setup command that installs a wrapper around Claude Code's status line. A status line is the information bar shown while Claude Code runs.

In plain words
What is it for?
Use it to check the current setup, install or uninstall the wrapper, and optionally keep an existing command such as `cs render` working.
Why use it?
It can capture Anthropic rate-limit information while preserving an existing status line, and it provides an uninstall path.

Command for Claude Code

Written for Claude Code: ${CLAUDE_PLUGIN_ROOT} variable. Also seen: reads .claude/ paths; mentions Claude Code.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the claude-timeline plugin — 4 commands shipped together

not rated 4repo 5mo ago B scan 27 tokens original MIT

Good fit Use it to check the current setup, install or uninstall the wrapper, and optionally keep an existing command such as cs render working.

Compare 6 commands from other repositories ↓
View source ↗ BlazeMV/blaze-claude-plugins
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add BlazeMV/blaze-claude-plugins
Claude Code
/plugin install claude-timeline

Made for: Claude Code.

Or install claude-timeline, the plugin that ships this one along with the rest of its 4 commands.

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 timeline-setup

README.md
[![agentmods](https://agentmods.dev/badge/commands/blazemv/blaze-claude-plugins/timeline-setup/github.svg)](https://agentmods.dev/commands/blazemv/blaze-claude-plugins/timeline-setup)
Your own site
<a href="https://agentmods.dev/commands/blazemv/blaze-claude-plugins/timeline-setup"><img src="https://agentmods.dev/badge/commands/blazemv/blaze-claude-plugins/timeline-setup/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 timeline-setup

Your own site · 80×15
<a href="https://agentmods.dev/commands/blazemv/blaze-claude-plugins/timeline-setup"><img src="https://agentmods.dev/badge/commands/blazemv/blaze-claude-plugins/timeline-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 27 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 238 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. 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.00027 $0.00238
Opus 5.5 $0.00011 $0.00095
Sonnet 5.5 $0.00005 $0.00048
Haiku 4.5 $0.00003 $0.00024

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

Security

Grade B, and why

timeline-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 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.

Reads agent configuration directoriesmediumAgent snooping

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

- `~/.claude/settings.json` `statusLine.command` will be set to `node ${CLAUDE_PLUGIN_ROOT}/scripts/capture.mjs`.
plugins/claude-timeline/commands/timeline-setup.md · 15 lines

What it actually says

Before making changes, run node ${CLAUDE_PLUGIN_ROOT}/scripts/setup.mjs status and show the current state to the user.

Then explain what will change:

  • ~/.claude/settings.json statusLine.command will be set to node ${CLAUDE_PLUGIN_ROOT}/scripts/capture.mjs.
  • If a previous statusLine command exists (e.g. cs render from leeguooooo/claude-code-usage-bar), it will be saved to ~/.claude/claude-timeline.json as downstream_statusline and chained transparently — their existing status bar keeps working.
  • To revert: node ${CLAUDE_PLUGIN_ROOT}/scripts/setup.mjs uninstall.

Ask the user to confirm before proceeding. On confirmation, run node ${CLAUDE_PLUGIN_ROOT}/scripts/setup.mjs install and remind them to restart Claude Code for the change to take effect.

If the user passes uninstall, run the uninstall path instead.

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 · 15 lines · 27 tokens per session scan B 179c20733f55

Subscribe to this mod's changes

timeline-setup is a command published in the GitHub repository BlazeMV/blaze-claude-plugins (4 stars, last pushed 5mo ago), licensed MIT. It adds 27 tokens to every session and 238 once invoked, about $0.0001 per session on Opus 5.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.

Related

Other commands, from other repositories

checklist

Generate a custom checklist for the current feature based on user requirements.

github/spec-kit · 13 tokens

clarify

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

github/spec-kit · 27 tokens

specify

Create or update the feature specification from a natural language feature description.

github/spec-kit · 13 tokens

converge

Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.

github/spec-kit · 35 tokens

implement

Execute the implementation plan by processing and executing all tasks defined in tasks.md.

github/spec-kit · 14 tokens

speckit.bug.fix

Apply the remediation from a bug assessment and record what was changed.

github/spec-kit · 12 tokens