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 loopdive/js2 --skill session-wrapupgit clone --depth 1 https://github.com/loopdive/js2Wrote 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/loopdive/js2/session-wrapup)<a href="https://agentmods.dev/skills/loopdive/js2/session-wrapup"><img src="https://agentmods.dev/badge/skills/loopdive/js2/session-wrapup/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/loopdive/js2/session-wrapup"><img src="https://agentmods.dev/badge/skills/loopdive/js2/session-wrapup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00054 | $0.01244 |
| Opus 5.5 | $0.00022 | $0.00498 |
| Sonnet 5.5 | $0.00011 | $0.00249 |
| Haiku 4.5 | $0.00005 | $0.00124 |
Grade A, and why
session-wrapup 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 1mo 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session Wrap-Up
Persist all session-level learnings and state to disk BEFORE running /compact or ending a session. Ensures nothing is discarded with the conversation.
When to use
- At end-of-day / session end (user signals "we're done for today")
- Before running
/compact(especially mid-sprint) - After a long merge wave or planning session
- When approaching a token budget threshold (≥40% weekly)
Distinct from sprint-wrap-up which is for closing a sprint with retrospective + tagging. This skill is for routine session ends while a sprint is still active.
Step 1: Verify on main in /workspace
pwd && git branch --show-current
Must be /workspace on main. Abort if not.
Step 2: Append to plan/diary.md
Add a new ## YYYY-MM-DD HH:MM — <brief title> section at the bottom with:
- Pass rate — start and end numbers if changed
- Merges — PRs that landed, with net deltas
- Closes — PRs rejected, with reasons
- New issues filed — numbers + one-line purpose
- Incidents — OOM, stuck processes, false-positive regressions, CI glitches
- Context/budget — tokens burned, triggers, mitigations applied
- Key learnings — non-obvious findings worth saving (1-sentence each)
Keep it to ~30-60 lines. Bullets, not prose.
Step 3: Update plan/issues/sprints/N/sprint.md
Fill the ## Results section (mark as "interim" if sprint still active):
## Results (interim — YYYY-MM-DD, sprint still active)
**Baseline progress:** <start> → **<end>** pass / <total> total = **<pct>%** (<+delta>)
Sprint goal (<goal>) <met|not yet met>. <gap> tests <remaining>.
### Merged
- **#NNN <title>** (<PR>, <+delta> pass)
...
### Closed without merging
- **#NNN <reason>**
...
And if the sprint has a ## Retrospective section, append an interim retro with "What went well / What went badly / Process improvements / Key numbers / Sprint-close criteria remaining".
Step 4: Append the retrospective section in plan/issues/sprints/N/sprint.md
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.
- 1mo ago First seen · 144 lines · 54 tokens per session scan A 022668932918
session-wrapup is a skill published in the GitHub repository loopdive/js2 (66 stars, last pushed today), licensed Apache-2.0. It adds 54 tokens to every session and 1,244 once invoked, about $0.0002 per session on Opus 5.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
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
review-triage-phase
Produces canonical review actions from fetched review state and renders action markdown. Use when the user wants only triage/action-planning for the review-framework workflow.
multiline-commit-messages
Use single-quoted strings for multiline git commit messages in the Shell tool. Prevents heredoc escaping failures that produce garbled commit messages.
stacking-prs
Create and manage GitHub native Stacked PRs in this repo with the gh stack CLI. Use when asked to stack PRs, split a large change into a stack, add a layer to a stack, restack or rebase a stack, adopt existing branches or PRs into a stack, check out someone else's stack, or land a stack. Covers creating and submitting…
github-copilot-upgrader
Use this to update the Github Copilot CLI/SDK.