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/ils15/pantheon-legacyWrote 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/ils15/pantheon-legacy/pantheon-optimize)<a href="https://agentmods.dev/commands/ils15/pantheon-legacy/pantheon-optimize"><img src="https://agentmods.dev/badge/commands/ils15/pantheon-legacy/pantheon-optimize.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.00043 | $0.00279 |
| Opus 5 | $0.00022 | $0.00139 |
| Sonnet 5 | $0.00009 | $0.00056 |
| Haiku 4.5 | $0.00004 | $0.00028 |
Grade A, and why
pantheon-optimize 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.
This is a copy
88% identical to optimize — 12 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
/pantheon-optimize — Documentation Optimization
What: Scans all .md and .json files for context bloat, redundant documentation, and oversized files. By default, compresses and consolidates findings. Use --dry-run for audit-only report.
Usage:
/pantheon-optimize— Full scan + compress/consolidate (default)/pantheon-optimize --dry-run— Scan and report only, no changes/pantheon-optimize --path=<dir>— Limit scan to a specific directory
Scope:
- All
.mdand.jsonfiles scanned for bloat, redundancy, and size - Compression and consolidation applied to
.pantheon/memory-bank/ - Reports token savings and optimization opportunities
Replaces: /token-audit (use /pantheon-optimize --dry-run for audit-only reports). The previous /pantheon-optimize behavior (memory-bank compression) is now the default mode.
Note: Non-destructive — archives obsolete content, never deletes meaningful data.
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 · 22 lines · 43 tokens per session scan A bc27c36e20d4
pantheon-optimize is a command published in the GitHub repository ils15/pantheon-legacy (10 stars, last pushed 5d ago), licensed MIT. It adds 43 tokens to every session and 279 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to optimize, differing in 12 lines, and is treated as a copy.
Other commands, from other repositories
minutes-ideas
Surface recent voice memos and ideas captured from any device. Use when the user asks "what ideas did I have?", "what were my recent memos?", "what did I record while walking?", or wants to recall a captured thought.
learn
Force claude-smart to extract learnings from this session now.
memory-store
Store an insight, decision, or pattern to memory.
cc-memory
Configure persistent memory that survives across sessions using a layered approach: split rule files for always-loaded context, auto-memory for organic learning, and optional MCP-backed long-term memory for large codebases.
analyze-context
USE WHEN you want to analyze project context before starting work on a task. Calls context + recall, then synthesizes goals, decisions, gotchas, and relevant memories into a pre-task brief.
lians-recall
Recall current (non-stale) facts from Lians memory, optionally as-of a past date.