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/avelikiy/great_cto/savegit clone --depth 1 https://github.com/avelikiy/great_ctoWrote 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/avelikiy/great_cto/save)<a href="https://agentmods.dev/commands/avelikiy/great_cto/save"><img src="https://agentmods.dev/badge/commands/avelikiy/great_cto/save.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.00026 | $0.01854 |
| Opus 5 | $0.00013 | $0.00927 |
| Sonnet 5 | $0.00005 | $0.00371 |
| Haiku 4.5 | $0.00003 | $0.00185 |
Grade A, and why
save 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 yesterday.
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 — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the great_cto /save command. Your job is to create a compact, useful session log that makes /resume fast next time. Write, don't ask — infer everything from the conversation and git.
Step 1 — Gather session data (run all in parallel)
# What changed in git during this session
git diff --stat HEAD 2>/dev/null | head -20
git log --oneline --since="8 hours ago" 2>/dev/null | head -10
# Current open tasks
cat .great_cto/tasks.md 2>/dev/null | grep -E "^\- \[.\]" | head -20
# Existing logs (to auto-number)
ls .great_cto/logs/session-*.md 2>/dev/null | wc -l
# Project name + phase
grep -E "^# |^phase:|^primary:" .great_cto/PROJECT.md 2>/dev/null | head -3
Step 2 — Infer session description
If the user provided $ARGUMENTS — use that as the session description.
Otherwise infer from:
- Git commits made during this session (last 8 hours)
- What was discussed/built in this conversation
- File changes visible in
git diff --stat
Keep the description to 3–5 words: "implemented auth flow", "fixed streaming archetype", "added regulated auto-detect".
Step 3 — Write session log
mkdir -p .great_cto/logs
DATE=$(date +%Y-%m-%d)
TIME=$(date +%H:%M)
SLUG=$(echo "<session-description>" | tr ' ' '-' | tr '[:upper:]' '[:lower:]' | sed 's/[^a-z0-9-]//g' | cut -c1-40)
LOG_FILE=".great_cto/logs/session-${DATE}-${SLUG}.md"
Write $LOG_FILE:
---
date: <YYYY-MM-DD>
time: <HH:MM>
duration: <estimated from conversation length — "~30 min" / "~2 h">
concepts: [<keyword1>, <keyword2>, <keyword3>]
---
# Session: <description>
## Done
- <bullet: what was actually implemented / fixed / decided>
- <bullet: second thing>
- <bullet: third thing if applicable>
## Decisions
- <any explicit decisions made — e.g. "decided to use X over Y because Z">
*(none)* — if nothing was explicitly decided
## Pending
- <what was left unfinished or is the clear next step>
- <second pending item if any>
## Files changed
<output of git diff --stat HEAD or "no git changes">
## Commits
<git log --oneline --since="8 hours ago" output, or "no commits this session">
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.
- yesterday First seen · 213 lines · 26 tokens per session scan A 1321455f5813
save is a command published in the GitHub repository avelikiy/great_cto (89 stars, last pushed today), licensed MIT. It adds 26 tokens to every session and 1,854 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-09-03.
Other commands, from other repositories
develop
Implement skill development issues with TDD-governed workflow.
acos-checkpoint
Create checkpoints before risky operations. Rollback if things go wrong.
pb-today
Delegate to oh-my-personal-best:session-coach to prescribe today's session.
push
Commit, push, and post a progress comment using session context or branch detection.
resume
Auto-detect and resume any interrupted Plan Cascade task. Detects mega-plan, hybrid-worktree, or hybrid-auto context and routes to the appropriate resume command.
recap
Time-windowed "where was I?" — git commits, session notes, and files touched in the last N hours or days. Use after stepping away for a few hours or days. Not for cold starts after a long absence (use /tools:brief) or live development checks (use /tools:status).