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 commands/eezz4/zzop/updategit clone --depth 1 https://github.com/eezz4/zzopWhat 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.00021 | $0.00754 |
| Opus 5 | $0.00010 | $0.00377 |
| Sonnet 5 | $0.00004 | $0.00151 |
| Haiku 4.5 | $0.00002 | $0.00075 |
Grade A, and why
update scanned grade A 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 yesterday.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
`curl -fsSL --max-time 10 https://api.github.com/repos/eezz4/zzop/releases/latest` and take How it starts
The opening of the file, as written. The whole thing — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Check for a newer zzop-mcp, and report only
Tell the user which zzop-mcp they have, whether a newer release exists, and — if it does — exactly
what to do about it. Do not act on the answer. Not with this command, not as a follow-up, not
even if the user seems to want it: taking the update is a decision about when, and the reasons are
below.
Why this never installs
A zzop version change is not a patch to a tool that produces the same answer faster. It changes what the analyzer finds, and it invalidates the analysis cache — every cache fingerprint is derived from the source that produced the cached bytes, so a new binary means a full cold run. An update that happened without being asked for would change findings between two sessions with no change in the user's code, which is the exact opposite of the determinism this tool sells. The timing belongs to whoever is going to read the diff in the findings.
The plugin's SessionStart hook follows the same rule: it installs when nothing is installed, and
after that it only ever reports. This command is the on-demand half of the same contract.
Steps
- Find the installed binary. It lives at
$CLAUDE_PLUGIN_DATA/zzop-mcp(zzop-mcp.exeon Windows). That location is decided by.claude-plugin/hooks/bootstrap.sh— read it rather than assuming, if the path does not resolve. - Read the installed version with
zzop-mcp version. If the binary is missing or cannot report a version, say so and stop: the fix is a new session (the hook installs onSessionStart), not anything this command should do. - Read the latest published version:
curl -fsSL --max-time 10 https://api.github.com/repos/eezz4/zzop/releases/latestand taketag_name. If the request fails, say the check could not run — offline, proxied, or rate-limited — and do not guess from any other source. - Report the comparison. Same version: one line saying it is current. Newer available: name both
versions, then give the two ways to take it:
- delete the binary at
$CLAUDE_PLUGIN_DATA/zzop-mcpand start a new session — the hook installs the current release, or - download it from
https://github.com/eezz4/zzop/releasesand put it at that path yourself.
- delete the binary at
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.
- yesterday First seen · 54 lines · 21 tokens per session scan A 25c4c976ee50
update is a command published in the GitHub repository eezz4/zzop (2 stars, last pushed 16d ago), licensed MIT. It adds 21 tokens to every session and 754 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
review
Run a CKB-augmented code review optimized for minimal token usage.
audit
Run a CKB-augmented compliance audit optimized for minimal token usage.
code-diagram
You are a code analysis expert. Analyze real source code and generate accurate Mermaid diagrams. Never guess or invent — every element must come directly from the code.
report
Generate a comprehensive quality report for a .NET project — code smells, technical debt, architecture rules, and dependency health.
analyze
Analyze a .NET project or solution — list projects, check diagnostics, and present a structured summary.
security
Scan a .NET project for security vulnerabilities and dependency health issues.