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/projanvil/mindforge/session-summarynpx skills add ProjAnvil/MindForge --skill session-summarygit clone --depth 1 https://github.com/ProjAnvil/MindForgeWhat 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.00058 | $0.00437 |
| Opus 5 | $0.00029 | $0.00218 |
| Sonnet 5 | $0.00012 | $0.00087 |
| Haiku 4.5 | $0.00006 | $0.00044 |
Grade A, and why
session-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 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.
What it actually says
Session Summary & Handover
You are an expert at context management and project continuity. Your goal is to capture the essence of the current development session so that work can continue seamlessly in a fresh environment.
Your Responsibilities
- Analyze the current state: Review the recent interactions, file changes, and accomplished goals.
- Summarize Key Information:
- Goal: What was the main objective of this session?
- Progress: What exactly was achieved? (Files created, bugs fixed, features implemented)
- Context: Key technical decisions made, environment variables set, or specific constraints discovered.
- Open Issues: Any unresolved errors, blocked tasks, or partial implementations.
- Define Next Steps: A clear, prioritized list of what needs to be done immediately in the next session.
- Generate Handover Prompt: detailed prompt that the user can paste into the next session to restore context.
Handover Format
When asked to summarize the session, structure your response as follows:
1. Session Snapshot
- Objective: ...
- Status: [Completed / In-Progress / Blocked]
2. Accomplishments
- ...
- ...
3. Technical Context
- ...
4. Next Session To-Do
- Task 1
- Task 2
5. Restore Prompt (Copy & Paste this into new session)
[CONTEXT RESTORATION]
Project Path: <Current Path>
Last Session Summary:
<Insert Summary Here>
Immediate Tasks:
<Insert Next Steps Here>
Please review the current files and continue from where we left off.
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 · 52 lines · 58 tokens per session scan A 0c0698aebe16
session-summary is a skill published in the GitHub repository ProjAnvil/MindForge (3 stars, last pushed 5mo ago), licensed MIT. It adds 58 tokens to every session and 437 once invoked, about $0.0003 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
opik-diagnose
Surface the Opik traces worth a developer's attention, ranked by signal — errors, failed tool calls, latency, regressions, and low online-eval scores — plus Diagnostics issues. Reads live/production traces via the SDK (searchtraces and agentinsights) and works with no MCP; uses the MCP issue entity when connected.…
client-scripts
Write ServiceNow client scripts (onLoad/onChange/onSubmit/onCellEdit) using gform, guser, GlideAjax, field visibility/mandatory toggles, and validation with debounced server calls.
agoragentic-transaction-assurance
Prepare, evaluate, and reconcile autonomous agent transactions without self-granting payment or owner authority. Use when an agent must bind principal authority, seller terms, payment evidence, execution, delivered outcome, and reconciliation; handle paid retries safely; or prepare an authority request for owner…
linkding
Manage bookmarks with Linkding. Use when the user asks to "save a bookmark", "add link", "search bookmarks", "list my bookmarks", "find saved links", "tag a bookmark", "archive bookmark", "check if URL is saved", "list tags", "create bundle", or mentions Linkding bookmark management.
debugging-mutations
Verify what changed on a ServiceNow instance after a tool call — sysaudit inspection, syslog/transaction logs, session context, Flow Designer execution logs, outbound HTTP traces.
maya-shot-export
Pipeline stage — shot-level export: frame ranges, cameras, FBX / Alembic packaging for editorial. Use when packaging shot data for downstream departments. Not for full pipeline publish (maya-pipeline) or scene assembly (maya-scene-assembly).