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/iam-dev/cc-sessions/sessionsgit clone --depth 1 https://github.com/iam-dev/cc-sessionsWhat 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.00011 | $0.00523 |
| Opus 5 | $0.00005 | $0.00262 |
| Sonnet 5 | $0.00002 | $0.00105 |
| Haiku 4.5 | $0.00001 | $0.00052 |
Grade A, and why
sessions 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session Memory
Display the last session summary for the current working directory.
Instructions
When the user runs /sessions, use the cc-sessions CLI to retrieve and display the last session:
node "${CLAUDE_PLUGIN_ROOT}/dist/cli.js" show
Output Format
Display the session information in this format:
┌─────────────────────────────────────────────────────────────────┐
│ LAST SESSION │
├─────────────────────────────────────────────────────────────────┤
│ Project: {projectName} │
│ When: {relativeTime} ({duration}) │
│ Tokens: {tokensUsed} │
├─────────────────────────────────────────────────────────────────┤
│ │
│ SUMMARY │
│ {summary text, wrapped to fit} │
│ │
│ COMPLETED │
│ - {completed task 1} │
│ - {completed task 2} │
│ │
│ PENDING │
│ - {pending task 1} │
│ - {pending task 2} │
│ │
│ FILES MODIFIED │
│ - {file1.ts} (created) │
│ - {file2.ts} (modified) │
│ │
│ SUGGESTED NEXT STEPS │
│ 1. {next step 1} │
│ 2. {next step 2} │
│ │
├─────────────────────────────────────────────────────────────────┤
│ [/sessions:resume] Resume [/sessions:search] Search │
└─────────────────────────────────────────────────────────────────┘
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 · 83 lines · 11 tokens per session scan A b603ceed929f
sessions is a command published in the GitHub repository iam-dev/cc-sessions (2 stars, last pushed 4mo ago), licensed MIT. It adds 11 tokens to every session and 523 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-08-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.