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 skills/itsribbz/godspeed/close-sessionnpx skills add itsribbZ/Godspeed --skill close-sessiongit clone --depth 1 https://github.com/itsribbZ/GodspeedWrote 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/skills/itsribbz/godspeed/close-session)<a href="https://agentmods.dev/skills/itsribbz/godspeed/close-session"><img src="https://agentmods.dev/badge/skills/itsribbz/godspeed/close-session.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.00061 | $0.03446 |
| Opus 5 | $0.00030 | $0.01723 |
| Sonnet 5 | $0.00012 | $0.00689 |
| Haiku 4.5 | $0.00006 | $0.00345 |
Grade B, and why
close-session scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
TICK=$(cat ~/.claude/telemetry/brain/godspeed_count.txt 2>/dev/null || echo 0) How it starts
The opening of the file, as written. The whole thing — 307 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Close Session v2.0
Init loads context. Close-session saves it. Together: lossless session loop.
Context-discipline (v2.2 — 2026-04-17): Close-session writes summaries from what's already in the conversation. It does NOT re-load source material. Without this discipline, long sessions push main-session context past 200K and force the
[1m]model variant, which requires/extra-usagebilling. The rules below keep close-session inside the standard 200K window.
Context-Discipline Rules (v2.2)
- Phase 1 session audit — scan the scrollback you already have. Don't re-Read any file already touched this session — use what's in context.
- Phase 4 memory updates — Edit files in-place with targeted file:line anchors. Do NOT Read a file end-to-end just to understand where to append — use Grep to find the insertion point, then Edit.
- Phase 4c skill
_learnings.mdchecks — always grep-first, never bulk-read:
Only Read the full file if a regression is suspected.grep -c "^###" ~/.claude/skills/<skill>/_learnings.md # entry count tail -40 ~/.claude/skills/<skill>/_learnings.md # recent entries only - Project docs sync — if a project's canonical docs are >10K tokens, Edit them with targeted file:line anchors. Don't Read the whole file to understand context.
Bottom line: close-session writes summaries, it does NOT re-load session source material. Everything needed is already in the conversation context.
Trigger
"close session", "end session", "wrap up", "save session", "done for today", "session done"
Phase 1: Session Audit
Scan the conversation for:
- Work Completed — features built, bugs fixed, code written, files created/modified
- Decisions Made — design choices, architecture decisions, approach changes
- Bugs Found/Fixed — new bugs discovered, existing bugs resolved
- Research Done — outputs from any research / analysis skill used this session
- Tools Created/Updated — new scripts, skill improvements, workflow changes
- Unfinished Work — started but not completed, mid-progress state
- Next Steps — planned next actions, logical continuations
- User Feedback — corrections, preferences, guidance that should persist
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 · 307 lines · 61 tokens per session scan B bdcc1f48c3c2
close-session is a skill published in the GitHub repository itsribbZ/Godspeed (1 stars, last pushed 2mo ago), licensed MIT. It adds 61 tokens to every session and 3,446 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
memory-recall
Search and recall relevant memories from past sessions via memsearch. Use when the user's question could benefit from historical context, past decisions, debugging notes, previous conversations, or project knowledge -- especially questions like 'what did I decide about X', 'why did we do Y', or 'have I seen this…
alive:session-history
Revive sessions (quick or heavy), browse, and search — 'what happened recently?', 'find the session where we discussed X', 'revive yesterday's session'. For single-session recall and multi-session browsing. If the human needs to merge multiple sessions into one working context or detect conflicts between parallel…
cross-session-handoff
Read, write, snapshot, and lock .arcgentic/state.yaml across planner, dev, audit, and optional test sessions.
recall
Must be used at the start of any non-trivial task involving code changes, debugging, repo exploration, file inspection, or environment/tooling investigation to surface stored guidance before analysis or tool use.
cco-templates
Manage context templates for common task types.
alive-people
Weekly -- cross-reference people mentions, nudge stale contacts.