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/iam-dev/cc-sessions/sessions-project-summarynpx skills add iam-dev/cc-sessions --skill sessions-project-summarygit clone --depth 1 https://github.com/iam-dev/cc-sessionsWrote 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/iam-dev/cc-sessions/sessions-project-summary)<a href="https://agentmods.dev/skills/iam-dev/cc-sessions/sessions-project-summary"><img src="https://agentmods.dev/badge/skills/iam-dev/cc-sessions/sessions-project-summary.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.00034 | $0.00343 |
| Opus 5 | $0.00017 | $0.00171 |
| Sonnet 5 | $0.00007 | $0.00069 |
| Haiku 4.5 | $0.00003 | $0.00034 |
Grade A, and why
sessions-project-summary 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 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.
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.
What it actually says
Fetch all sessions for the current project:
node "${CLAUDE_PLUGIN_ROOT}/dist/cli.js" list --limit 9999
Then, using the session data returned, write a project summary covering:
Project Summary Format
PROJECT SUMMARY: {projectName}
═══════════════════════════════════════════════════════════════
OVERVIEW
{2-3 sentence description of what this project is and what has been built}
WORK COMPLETED
- {major feature or milestone 1}
- {major feature or milestone 2}
- {major feature or milestone 3}
IN PROGRESS / PENDING
- {unfinished task 1}
- {unfinished task 2}
KEY DECISIONS
- {architectural or design decision 1}
- {architectural or design decision 2}
FILES MOST TOUCHED
- {file1} — {reason}
- {file2} — {reason}
SESSIONS
Total: {count} sessions
First: {date of first session}
Latest: {date of most recent session}
Total tokens: {sum}
SUGGESTED NEXT STEPS
1. {next step 1}
2. {next step 2}
═══════════════════════════════════════════════════════════════
Synthesize the summary yourself from the session data — do not just list sessions. Group related work, identify patterns, and surface what matters most.
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 · 54 lines · 34 tokens per session scan A 3f420f1f4e90
sessions-project-summary is a skill published in the GitHub repository iam-dev/cc-sessions (2 stars, last pushed 4mo ago), licensed MIT. It adds 34 tokens to every session and 343 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-31.
Other skills, from other repositories
wayfinder
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
timeline-creator
Create HTML timelines and project roadmaps with Gantt charts, milestones, phase groupings, and progress indicators. Use when users request timelines, roadmaps, Gantt charts, project schedules, or milestone visualizations.
pm-all
Skill "pm-all" from wei63w/pm-manager, covering user input, outline and shared workflow (all /pm- commands).
bootstrap-prd
Set up PRD-driven development infrastructure for a new project, including directory structure, templates, and roadmap.
simulator-reactions
Simulator.Company reactions specialist — comments, events, approvals, ratings and other feedback attached under an actor. Use when the user wants to comment on an actor, reply in a thread, read/like/pin the discussion, mark comments read, or get reaction stats. Activate when the user says "comment on this actor"…
glab-issue
Create, view, update, and manage GitLab issues. Use when working with issue tracking, bug reports, feature requests, or task management. Operations include creating issues, listing with filters, viewing details, adding comments/notes, updating labels/assignees/milestones, closing/reopening, and board management.…