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.
git clone --depth 1 https://github.com/sungmanch/claude-glm-agentWrote 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/commands/sungmanch/claude-glm-agent/glm)<a href="https://agentmods.dev/commands/sungmanch/claude-glm-agent/glm"><img src="https://agentmods.dev/badge/commands/sungmanch/claude-glm-agent/glm.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.00025 | $0.00277 |
| Opus 5 | $0.00013 | $0.00138 |
| Sonnet 5 | $0.00005 | $0.00055 |
| Haiku 4.5 | $0.00003 | $0.00028 |
Grade A, and why
glm 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 8d 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.
What it actually says
GLM Single Call
Request: $ARGUMENTS
Execution Method
Call the GLM API using the command below:
~/.claude/plugins/local/claude-glm-agent/scripts/glm_call.sh "<question>" [model]
Available Models
| Model | Features |
|---|---|
glm-4.7 |
Best performance (default) |
glm-4.5-air |
Fast response, for simple tasks |
Examples
# Default usage (GLM-4.7)
~/.claude/plugins/local/claude-glm-agent/scripts/glm_call.sh "Analyze this code"
# Using fast model
~/.claude/plugins/local/claude-glm-agent/scripts/glm_call.sh "Summarize briefly" "glm-4.5-air"
Instructions
- Pass the user's request ($ARGUMENTS) to GLM
- Deliver GLM's response directly to the user
- Provide comparison/analysis with Opus's perspective when needed
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.
- 8d ago First seen · 41 lines · 25 tokens per session scan A da51e57c5afb
glm is a command published in the GitHub repository sungmanch/claude-glm-agent (5 stars, last pushed 5mo ago), licensed MIT. It adds 25 tokens to every session and 277 once invoked, about $0.0001 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-31.
Other commands, from other repositories
awesome-chatgpt
Search awesome-ChatGPT-repositories for open-source GitHub repositories related to ChatGPT and LLMs.
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
init
Scaffold a new MindBase project (v2 layout). Usage: /mb:init [template] [-- mission ...].
pr
Handle the full workflow from current branch state to an open, CI-monitored pull request.
recall
Search past tool-call observations with BM25 ranking to answer "have I seen this before?" before re-deriving a fix or repeating a mistake. Enforces Law 1 (Research Before Executing).
requirement-review
A command that has several specialized agents review a requirements document and produce a revised version through a controlled workflow.