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 robotaitai/project-bedrock --skill session-managementgit clone --depth 1 https://github.com/robotaitai/project-bedrockWrote 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/robotaitai/project-bedrock/session-management)<a href="https://agentmods.dev/skills/robotaitai/project-bedrock/session-management"><img src="https://agentmods.dev/badge/skills/robotaitai/project-bedrock/session-management.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.00037 | $0.00813 |
| Opus 5 | $0.00018 | $0.00407 |
| Sonnet 5 | $0.00007 | $0.00163 |
| Haiku 4.5 | $0.00004 | $0.00081 |
Grade A, and why
session-management 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session Management
Session files preserve in-progress context through long sessions and help new sessions resume quickly from prior work.
The session file path is provided by the session-start hook
(e.g., ~/.cursor/projects/<project-id>/sessions/).
For project-shared session notes, use agent-knowledge/Sessions/.
Session vs memory — the key distinction
| Session file | Memory tree |
|---|---|
| Ephemeral — deleted or archived when no longer active | Durable — persists across all sessions |
| Tracks current task progress | Tracks stable project understanding |
| Milestone-oriented log entries | Fact-oriented structured files |
| Private to one conversation thread | Shared across all agents and conversations |
| Write freely, prune aggressively | Write carefully, never speculate |
Rule: if a fact belongs to future sessions, it goes in memory. If it only matters for this session, it stays in the session file.
Session file format
Filename: YYYY-MM-DD-<title-slug>-<UUID>.tmp
(slug defaults to session until the task is clear, then updated)
## Current State
[One-line description of current focus]
### Completed
- [Milestone outcomes, not step-by-step details]
### In Progress
- [What is actively being worked on]
### Blockers
- [What is preventing progress]
### Notes for Next Session
- [What to load immediately when resuming]
### Context to Load
- [Which memory areas and files to read on resume]
## Session Log
**HH:MM** - [Milestone outcome in one line]
How to update
- Read the current session file first.
- If nothing meaningful happened since the last log entry, do not write.
- If a meaningful milestone occurred, write one checkpoint:
- Refresh Current State
- Update Completed / In Progress / Blockers
- Add one timestamped Session Log line
- Set the session title once the task is clear.
- Keep entries milestone-oriented — not every tool call.
When NOT to write
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 · 117 lines · 37 tokens per session scan A 9d33d30752d2
session-management is a skill published in the GitHub repository robotaitai/project-bedrock (45 stars, last pushed 17d ago), licensed MIT. It adds 37 tokens to every session and 813 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
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
Migrate
Intakes external content, classifies chunks against LifeOS taxonomy, commits with provenance. Sources: .md/.txt, stdin, LifeOS dirs, CLAUDE.md/Cursor/OpenAI Custom Instructions, Obsidian/Notion/Apple Notes exports. MigrateScan classifies → routing table. MigrateApprove with…
daily-briefing
Proactive daily briefing that fires on a recurring schedule, pulls recent memory and workspace context, composes a structured summary (action items, progress, radar, next steps), and delivers it to all active channels. Enable with a time like "set up my daily briefing at 9am". Disable, reschedule, or check status at…
company-brain
Your team's shared, AI-ready knowledge base — people, companies, meetings, SOPs, and decisions structured so Claude can answer questions on your team's behalf. Team-scope sibling to second-brain (which is personal-scope). Seven modes — capture (drop something into the right structured dir), compile (process into wiki…
calendar
Manage calendar events via CalDAV (Google/iCloud/Nextcloud) or local ICS files. View, create, and query events.
email-assistant
Read, search, draft, and send emails via Himalaya CLI or Python IMAP/SMTP. Requires email account configuration.