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/elbalen/skopus/charter-evolvegit 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/charter-evolve)<a href="https://agentmods.dev/commands/elbalen/skopus/charter-evolve"><img src="https://agentmods.dev/badge/commands/elbalen/skopus/charter-evolve.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 | $0.00016 | $0.00956 |
| Opus 5 | $0.00008 | $0.00478 |
| Sonnet 5 | $0.00003 | $0.00191 |
| Haiku 4.5 | $0.00002 | $0.00096 |
Grade A, and why
charter-evolve 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/charter-evolve
The compounding mechanism for the partnership charter. Run this at the end of every substantive session. It captures what happened so the next session starts smarter.
This runs inside the agent, not the shell. The agent reviews the full conversation history and extracts knowledge — no manual input needed.
Steps
-
Review the full conversation history. Look for:
- Corrections — moments where the user said "no", "don't do that", "use X instead", or pushed back on an approach. Each correction is a drift.
- Validated calls — moments where the agent made a non-obvious choice and the user confirmed it worked ("yes exactly", "perfect", "keep doing that", accepted without pushback). These are easy to miss — watch for them.
- New rules — any explicit instruction the user gave about how to work going forward ("always X", "never Y", "from now on Z").
-
For each item found, write a feedback file at
~/.skopus/memory/feedback/YYYY-MM-DD-<slug>.mdusing this format:--- name: <kind>-<slug> description: <one-line description> type: feedback captured: YYYY-MM-DD --- # <Title> **Why:** <why this matters — the reason the user gave or the context> **How to apply:** <when and where this rule kicks in — be specific> -
Append drift entries to the charter. Open
~/.skopus/charter/workflow_partnership.mdand append each correction to Section 7 (Where We've Drifted) in this format:> **YYYY-MM-DD — <what I did wrong>.** <context>. **Correction:** <what the user said>. **Fix:** <the rule to follow next time>. -
Append validated calls to the charter. In the same file, append each win to Section 8 (What Has Worked):
- **YYYY-MM-DD — <what I did right>.** <why it worked>. *(How: <how to repeat it>)* -
Update the memory index. Add a one-line entry for each new feedback file to
~/.skopus/memory/MEMORY.mdunder the Feedback Memory section:
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.
- 4d ago First seen · 89 lines · 16 tokens per session scan A 092b203f41ef
charter-evolve is a command published in the GitHub repository elbalen/skopus (4 stars, last pushed 4mo ago), licensed MIT. It adds 16 tokens to every session and 956 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
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.
session-end
I'll summarize this coding session and update the memory system with our accomplishments.
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.
neo-review
Get Neo's code review with semantic matching against past findings in memory. Use on a diff or module before merge, especially where earlier mistakes in this codebase are likely to recur. Skip for formatting, lint-catchable issues, and single-line changes.