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/mayank-io/mstack/summarize-this-sessionnpx skills add mayank-io/mstack --skill summarize-this-sessiongit clone --depth 1 https://github.com/mayank-io/mstackWhat 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.00055 | $0.00467 |
| Opus 5 | $0.00028 | $0.00234 |
| Sonnet 5 | $0.00011 | $0.00093 |
| Haiku 4.5 | $0.00006 | $0.00047 |
Grade A, and why
summarize-this-session 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 2d 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
Summarize Current Conversation
Review everything that has happened in this conversation and produce a two-section summary.
Instructions
Look back through the entire conversation history — every user message, every tool call, every result, every correction.
Produce the following two sections:
Ongoing Task
Summarize the work in progress:
- Initial Request: What the user originally asked for. State it clearly and concisely.
- Progress Made: What has been accomplished so far. List concrete deliverables (files created, bugs fixed, features implemented, decisions made). Be specific — reference file paths, function names, and outcomes.
- Next Steps: What remains to be done. If the task is complete, say so. If there are open questions or follow-ups, list them.
Continuous Improvement
Analyze the conversation for learning opportunities:
-
Mistakes Made by Claude: Actions Claude took that were wrong, suboptimal, or had to be redone. Include:
- What happened
- What the correct approach was
- Why Claude got it wrong (wrong assumption, missing context, tool misuse, etc.)
-
Mistakes Pointed Out by Human: Corrections the user explicitly made. Include:
- What the user corrected
- What Claude was doing wrong
- Whether this is a recurring pattern
-
Lessons Learned: Actionable takeaways from this conversation that would improve future sessions. These could be:
- Workflow improvements
- Tool usage patterns
- Project-specific conventions discovered
- Things that should be added to CLAUDE.md or memory
- Skills or plugins that would have helped
Formatting Rules
- Be honest and specific — don't gloss over mistakes or be vague
- If there were no mistakes in a category, say "None" — don't fabricate issues
- Keep each bullet concise but include enough detail to be actionable
- Reference specific messages or tool calls when describing mistakes
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.
- 2d ago First seen · 55 lines · 55 tokens per session scan A af49a5f7927d
summarize-this-session is a skill published in the GitHub repository mayank-io/mstack (5 stars, last pushed 8d ago), licensed MIT. It adds 55 tokens to every session and 467 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…