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/jianzhichun/permafrostWrote 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/jianzhichun/permafrost/status)<a href="https://agentmods.dev/commands/jianzhichun/permafrost/status"><img src="https://agentmods.dev/badge/commands/jianzhichun/permafrost/status.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.00014 | $0.00202 |
| Opus 5 | $0.00007 | $0.00101 |
| Sonnet 5 | $0.00003 | $0.00040 |
| Haiku 4.5 | $0.00001 | $0.00020 |
Grade A, and why
status 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
allowed-tools: Bash(curl:*), Bash(*/cli/permafrost:*) What it actually says
Fetch the live Permafrost proxy stats and report them to the user.
Run this and interpret the JSON:
!curl -fsS "http://127.0.0.1:${PERMAFROST_PORT:-8787}/permafrost/stats" 2>/dev/null || echo '{"error":"proxy not reachable — start it with: permafrost up"}'
Summarize for the user in 3-4 lines: the cache hit rate, the hit/miss token split, the cost so far vs. the all-miss baseline (how much Permafrost saved), and the number of prefix resets (how many times the cache anchor changed — ideally 0). If the proxy isn't reachable, tell them to run permafrost up.
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 · 13 lines · 14 tokens per session scan A 0b7d963c56c1
status is a command published in the GitHub repository jianzhichun/permafrost (21 stars, last pushed 2mo ago), licensed MIT. It adds 14 tokens to every session and 202 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-30.
Other commands, from other repositories
help
Quick reference for all Attune commands.
spec
Spec-driven development — brainstorm, plan, review, and execute with quality gates and approval.
kill
Stop a running cli-dispatch worker session.
doc-gen
Generate documentation from source code — docstrings, README sections, API references.
refactor
Code-level refactoring analysis and roadmap generation.
pm-audit
Run the great-pm PM-health audit on a product, an initiative, or great-pm itself. 15 dimensions, severity-rated findings, Top-5 + Quick-Wins + Things-Look-Bad-But-Fine + Open Questions. Files findings as Beads tasks unless --read-only.