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 skills add Kastalien-Research/thoughtbox --skill session-reviewgit clone --depth 1 https://github.com/Kastalien-Research/thoughtboxWrote 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/kastalien-research/thoughtbox/session-review)<a href="https://agentmods.dev/skills/kastalien-research/thoughtbox/session-review"><img src="https://agentmods.dev/badge/skills/kastalien-research/thoughtbox/session-review.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.1 | $0.00046 | $0.00973 |
| Opus 5 | $0.00023 | $0.00487 |
| Sonnet 5 | $0.00009 | $0.00195 |
| Haiku 4.5 | $0.00005 | $0.00097 |
Grade A, and why
session-review 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 7d 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate a structured session summary for cross-session continuity.
Context
$ARGUMENTS
Loop Building Blocks
| Loop | Purpose | Reference |
|---|---|---|
| Consistency Check | Validate session summary against evidence | @loops/refinement/consistency-check.md |
| Documentation | Generate structured session review | @loops/authoring/documentation.md |
See @loops/README.md for the full loop library.
Workflow
Phase 1: Gather Session State (Observe)
- Run
git log --oneline -20to see recent commits this session - Run
git statusto see uncommitted work - Run
git diff --statto see scope of changes - Check
.Codex/state/memory-calibration.jsonfor pattern detection state - Read MEMORY.md for any updates made this session
Phase 2: Synthesize Session Context (Orient)
From the gathered data, identify:
- Key Decisions: What architectural or design choices were made and why
- Open Hypotheses: What questions remain unanswered, what investigations are pending
- Partial Work: What was started but not finished, with enough context to resume
- Knowledge Discovered: New patterns, gotchas, or insights worth preserving
- Blocked Items: What's blocked and on what
- Next Steps: What the next session should prioritize
Phase 3: Write Session Handoff (Act)
Write the session summary to .Codex/session-handoff.json (single file, overwritten each time) using this schema:
{
"version": "1.0.0",
"session_id": "<from git>",
"timestamp": "<ISO 8601>",
"branch": "<current git branch>",
"duration_estimate": "<approximate session duration>",
"summary": "<1-2 sentence summary of what happened>",
"key_decisions": [
{
"decision": "<what was decided>",
"reasoning": "<why>",
"alternatives_considered": ["<alt1>", "<alt2>"],
"files_affected": ["<file1>", "<file2>"]
}
],
"hypotheses": [
{
"hypothesis": "<what's being investigated>",
"evidence_for": ["<supporting evidence>"],
"evidence_against": ["<counter evidence>"],
"next_test": "<what to try next>"
}
],
"partial_work": [
{
"description": "<what was started>",
"status": "<how far along>",
"resume_from": "<specific file:line or commit to resume from>"
}
],
"knowledge_references": [
{
"store": "<MEMORY.md | Thoughtbox | git>",
"reference": "<specific entity/issue/commit>",
"relevance": "<why the next session needs this>"
}
],
"blocked_items": [
{
"item": "<what's blocked>",
"blocker": "<what's blocking it>",
"workaround": "<if any>"
}
],
"failed_approaches": [
{
"what": "<what was tried>",
"why": "<why it failed>",
"lesson": "<what to do instead>"
}
],
"next_priorities": ["<priority 1>", "<priority 2>", "<priority 3>"],
"warnings": ["<things the next session should watch out for>"]
}
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.
- 7d ago First seen · 133 lines · 46 tokens per session scan A 6c9fae37ef56
session-review is a skill published in the GitHub repository Kastalien-Research/thoughtbox (64 stars, last pushed 1mo ago), licensed MIT. It adds 46 tokens to every session and 973 once invoked, about $0.0002 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-30.
Other skills, from other repositories
forget
Delete specific observations from agentmemory after showing them and getting explicit confirmation. Use when the user says "forget this", "delete memory", "remove that note", or wants to scrub specific data for privacy.
handoff
Resume the most recent agent session for the current working directory, leading with any unanswered question. Use when the user says "where were we", "resume", "handoff", "pick up where I left off", or starts a session with no fresh context.
agentmemory-hooks
The agentmemory plugin hooks that capture observations automatically across the agent session lifecycle. Use when explaining how memory gets captured without manual saves, when debugging missing observations, or when tuning what gets recorded.
session-history
Show what happened in recent past sessions on this project as a clean timeline. Use when the user asks "what did we do last time", "session history", "past sessions", or wants an overview of previous work.
agentmemory-agents
How agentmemory wires into host coding agents via the connect command. Use when installing agentmemory into a specific agent, when asked which agents are supported, or when a connect adapter writes the wrong config path.
agentmemory-config
Skill "agentmemory-config" from rohitg00/agentmemory, covering quick start, defaults worth knowing, ports, see also and reference.