An installation command for the claude-pace status display. It checks for jq, copies the bundled script, and configures Claude Code to use it.

Setting up claude-pace on a machine where Claude Code is already installed.

It removes the manual steps needed to install and update the status display, while stopping clearly if a prerequisite is missing.

setup — Command by Astro-Han

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/astro-han/claude-pace/setup

Clone the repo

git clone --depth 1 https://github.com/Astro-Han/claude-pace

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

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

Security scan B 1 finding. Scan, not verified.

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.

Model	Per session	Once invoked
Fable 5	$0.00012	$0.00503
Opus 5	$0.00006	$0.00251
Sonnet 5	$0.00002	$0.00101
Haiku 4.5	$0.00001	$0.00050

Measured 2d ago against content hash 87b89ecd0123, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade B, and why

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 2d 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.

Read `~/.claude/settings.json` with the Read tool. Then use the Edit tool to add or update the `statusLine` key:

commands/setup.md · 57 lines

What it actually says

claude-pace Setup

You are installing claude-pace, a lightweight statusline for Claude Code. This skill is idempotent: safe to run for both first install and subsequent updates.

It installs the exact claude-pace.sh this plugin version ships. It makes no network calls, so the version the user gets is whatever /plugin update last resolved — not whatever happens to be on the repository's main branch right now.

Follow these steps in order. If any step fails, stop and explain the issue to the user.

Step 1: Check prerequisites

Run: command -v jq

If jq is not found, tell the user to install it (brew install jq on macOS, apt install jq on Linux) and stop.

Step 2: Install the bundled script

mkdir -p ~/.claude
cp "${CLAUDE_PLUGIN_ROOT}/claude-pace.sh" ~/.claude/statusline.sh
chmod +x ~/.claude/statusline.sh

If the cp fails because the source path does not exist, the plugin installation itself is broken. Stop and tell the user to reinstall the plugin. Do not fall back to downloading the script from the network.

Step 3: Configure statusline

Read ~/.claude/settings.json with the Read tool. Then use the Edit tool to add or update the statusLine key:

"statusLine": {
  "type": "command",
  "command": "~/.claude/statusline.sh"
}

If statusLine already exists, update the command value. If it does not exist, add it as a top-level key.

Step 4: Confirm

Tell the user:

claude-pace has been installed (or updated) successfully.
Restart Claude Code (or start a new session) to see the statusline.
To update later, pull the new plugin version first, then re-run this command: /plugin marketplace update claude-pace-marketplace → /plugin update claude-pace → /reload-plugins → /claude-pace:setup
To remove: delete the statusLine block from ~/.claude/settings.json.

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.

2d ago First seen · 57 lines · 12 tokens per session scan B 87b89ecd0123

Subscribe to this mod's changes

setup is a command published in the GitHub repository Astro-Han/claude-pace (229 stars, last pushed 1mo ago), licensed MIT. It adds 12 tokens to every session and 503 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-30.

bash claude claude-code cli developer-tools statusline

setup

Getting it into your agent

What it costs to keep this loaded

Grade B, and why

Reads agent configuration directoriesmediumAgent snooping

What it actually says

claude-pace Setup

Step 1: Check prerequisites

Step 2: Install the bundled script

Step 3: Configure statusline

Step 4: Confirm

What this file has done since we first saw it

Other commands, from other repositories

configure

setup

setup

cleanup

sync

tmux-agent