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/elbalen/skopusWrote 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/elbalen/skopus/compile)<a href="https://agentmods.dev/commands/elbalen/skopus/compile"><img src="https://agentmods.dev/badge/commands/elbalen/skopus/compile/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/elbalen/skopus/compile"><img src="https://agentmods.dev/badge/commands/elbalen/skopus/compile.svg" alt="Reviewed on agentmods" width="80" 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.00009 | $0.00410 |
| Opus 5.5 | $0.00004 | $0.00164 |
| Sonnet 5.5 | $0.00002 | $0.00082 |
| Haiku 4.5 | $0.00001 | $0.00041 |
Grade A, and why
compile 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 1mo 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
/compile
Capture valuable knowledge from the current session into the vault before it evaporates into chat history. The most important wiki command — it's what makes the wiki compound across sessions.
$ARGUMENTS is an optional topic focus.
Steps
-
Review the conversation for:
- Architectural decisions (with rationale and tradeoffs)
- Patterns discovered
- Gotchas encountered
- Problems solved (fix + root cause)
- Tools evaluated (chosen, rejected, why)
- Configurations that worked
- Non-obvious empirical facts (latencies, limits, version quirks)
-
Filter noise. Skip trivial fixes and anything already in git history. Bar: would future-me want to find this in 3 months?
-
If
$ARGUMENTSis provided, scope extraction to that topic. -
For each piece of knowledge: check
wiki/index.mdfor existing pages. Update existing (preferred) or create new. If contradicted, add> ⚠️ Contradiction:callout. -
Cross-link with
[[wikilinks]]. -
Update
wiki/index.md. -
Append to
log.md:## [YYYY-MM-DD HH:MM] compile | <Topic or "Session knowledge"> <Brief description.> Pages touched: [[page-1]], [[page-2]] -
Git commit:
compile: <topic or 'session knowledge'>. -
Print a summary of what was captured.
Rules
- Be honest about what's new vs. already-known.
- Don't inflate — if a session produced nothing wiki-worthy, say so and skip the commit.
- Capture the why, not just the what.
- Capture surprises — the most valuable entries are things that contradicted assumptions.
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.
- 1mo ago First seen · 49 lines · 9 tokens per session scan A 7056f2b784b3
compile is a command published in the GitHub repository elbalen/skopus (4 stars, last pushed 5mo ago), licensed MIT. It adds 9 tokens to every session and 410 once invoked, about $0.0000 per session on Opus 5.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
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.
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.
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.
lians-recall
Recall current (non-stale) facts from Lians memory, optionally as-of a past date.