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/saigonxiii/evc/save-sessiongit clone --depth 1 https://github.com/SaigonXIII/evcWhat 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.00000 | $0.00605 |
| Opus 5 | $0.00000 | $0.00302 |
| Sonnet 5 | $0.00000 | $0.00121 |
| Haiku 4.5 | $0.00000 | $0.00060 |
Grade A, and why
save-session 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 2d 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Save Session
Capture full session state so the next session can resume with zero context loss.
Trigger
User invokes /save-session or says "save session", "save state", "save progress"
Steps
1. Gather context
- Review all files modified during this session (git diff or conversation recall)
- Review what was discussed, attempted, and decided
- Note errors encountered and how they were resolved (or not)
- Check current build/test status if relevant
2. Create session file
mkdir -p {{SESSION_DIR}}
Write to {{SESSION_DIR}}/YYYY-MM-DD-<short-id>-session.md using today's date.
3. Populate every section below
Write every section honestly. "Nothing yet" or "N/A" for empty sections. An incomplete file is worse than an honest empty section.
# Session: YYYY-MM-DD
**Started:** [time if known]
**Last Updated:** [current time]
**Project:** [project name or path]
**Topic:** [one-line summary]
---
## What We Are Building
[1-3 paragraphs. Enough context for someone with zero memory to understand the goal.]
---
## What WORKED (with evidence)
[Only confirmed working things. Each item includes WHY you know it works.]
- **[thing]** — confirmed by: [specific evidence]
---
## What Did NOT Work (and why)
[MOST IMPORTANT SECTION. Every failed approach with the EXACT reason.]
- **[approach]** — failed because: [exact reason / error message]
---
## What Has NOT Been Tried Yet
[Promising approaches not yet attempted. Specific enough to act on.]
- [approach / idea]
---
## Current State of Files
| File | Status | Notes |
|------|--------|-------|
| `path/to/file` | Complete / In Progress / Broken / Not Started | [details] |
---
## Decisions Made
[Architecture choices, tradeoffs accepted, approaches chosen and why.]
- **[decision]** — reason: [why]
---
## Blockers & Open Questions
- [blocker / open question]
---
## Exact Next Step
[The single most important thing to do when resuming. Precise enough to start immediately.]
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.
- 2d ago First seen · 118 lines · 0 tokens per session scan A 24ed4151bd15
save-session is a command published in the GitHub repository SaigonXIII/evc (56 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 605 tokens. 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-30.
Other commands, from other repositories
review-tool
Research a tool or product for skill-gap, architecture, and verb-fit per the Anatomy framework.
setup
First-run setup — replace the fictional company and authors with yours.
review-content
Review content for brand alignment, lead placement, bio consistency, and proof points.
voice-check
Check a draft against the author's voice profile and flag deviations.
content-status
Scan all content directories and report status of drafts, ideas, and published content.
draft-blog
Scaffold a blog post with proper structure, voice, and frontmatter.