setup

A command for configuring the status line used by the GLM Coding Plan.

In plain words
What is it for?
Use it when setting up or adjusting the GLM Coding Plan status line.
Why use it?
It provides a way to change that status-line setup instead of configuring it manually.

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/jeongsk/glm-coding-plan-statusline/setup
Clone the repo
git clone --depth 1 https://github.com/jeongsk/glm-coding-plan-statusline
Per session 7 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 169 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.00007 $0.00169
Opus 5 $0.00003 $0.00084
Sonnet 5 $0.00001 $0.00034
Haiku 4.5 $0.00001 $0.00017

Measured 2d ago against content hash fea4c8d88790, 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.

Add to `~/.claude/settings.json`:
commands/setup.md · 31 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. 2d ago First seen · 31 lines · 7 tokens per session scan B fea4c8d88790

Subscribe to this mod's changes

setup is a command published in the GitHub repository jeongsk/glm-coding-plan-statusline (8 stars, last pushed 7mo ago), with no licence file. It adds 7 tokens to every session and 169 once invoked, about $0.0000 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.