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.
npx agentmods add instructions/jukanntenn/glm-plan-usage/claude-mdgit clone --depth 1 https://github.com/jukanntenn/glm-plan-usageWrote 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.
[](https://agentmods.dev/instructions/jukanntenn/glm-plan-usage/claude-md)<a href="https://agentmods.dev/instructions/jukanntenn/glm-plan-usage/claude-md"><img src="https://agentmods.dev/badge/instructions/jukanntenn/glm-plan-usage/claude-md.svg" alt="Measured on agentmods" height="20"></a>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.1 | $0.00857 | $0.00857 |
| Opus 5 | $0.00428 | $0.00428 |
| Sonnet 5 | $0.00171 | $0.00171 |
| Haiku 4.5 | $0.00086 | $0.00086 |
Grade A, and why
glm-plan-usage CLAUDE.md 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 6d 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.
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.
How it starts
The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
glm-plan-usage
A Claude Code status bar plugin that displays GLM (ZHIPU/ZAI) coding plan usage statistics. Shows token usage percentage, countdown to reset, and MCP usage in real-time.
Tech Stack
Core: Rust (edition 2021) + clap + ureq + serde + toml; Packaging: npm
Commands
# Build & Run
cargo build --release # Build release binary
./build-all.sh # Cross-platform build (7 targets)
# Lint & Format
cargo fmt # Format code
cargo clippy -- -D warnings # Run linter
# Testing
cargo test # Run all tests (unit + e2e)
cargo test --test e2e # Run e2e tests only
cargo test --lib # Run unit tests only
# CLI
glm-plan-usage init # Initialize config
glm-plan-usage print # Print current config
glm-plan-usage check # Validate config
Project Structure
For detailed module organization, see specs/directory-structure.md.
glm-plan-usage/
├── src/
│ ├── main.rs # Entry point, stdin parsing, CLI handling
│ ├── cli.rs # CLI argument definitions (clap derive)
│ ├── lib.rs # Library interface
│ ├── config/ # Configuration loading and types
│ ├── api/ # API client, cache, response types
│ └── core/ # Status line generation and segments
├── e2e/ # End-to-end CLI tests (assert_cmd + httpmock)
│ ├── main.rs # Test entry point
│ ├── helpers.rs # Shared test utilities
│ ├── fixtures/ # JSON fixtures (stdin input, API responses)
│ └── tests/ # Test modules by workflow
├── npm/ # NPM packaging (main + platform binaries)
├── specs/ # Design specifications
└── build-all.sh # Cross-platform build script
Standards
MUST FOLLOW THESE RULES, NO EXCEPTIONS
- Graceful degradation: the plugin must never cause Claude Code to fail. All segments return
Option<SegmentData>, never panic. - All config fields must have
#[serde(default)]to allow adding new fields without breaking existing configs. - Silent by default: no stderr output unless
--verboseis set. API failures returnNone, not errors. - Only add meaningful comments explaining why (not what) something is done.
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.
- 6d ago First seen · 74 lines · 857 tokens per session scan A 9e7cadf366fe
glm-plan-usage CLAUDE.md is an instructions file published in the GitHub repository jukanntenn/glm-plan-usage (13 stars, last pushed 2mo ago), licensed MIT. It adds 857 tokens to every session, about $0.0043 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-30.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.