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/loopdive/js2/session-wrapupnpx skills add loopdive/js2 --skill session-wrapupgit clone --depth 1 https://github.com/loopdive/js2What 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.00054 | $0.01244 |
| Opus 5 | $0.00027 | $0.00622 |
| Sonnet 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 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 — 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.
- yesterday First seen · 144 lines · 54 tokens per session scan A 022668932918
session-wrapup is a skill published in the GitHub repository loopdive/js2 (59 stars, last pushed yesterday), licensed Apache-2.0. It adds 54 tokens to every session and 1,244 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-30.
Other skills, from other repositories
migrate-oxfmt
Guide for migrating a project from Prettier or Biome to Oxfmt. Use when asked to migrate, convert, or switch a JavaScript/TypeScript project's formatter from Prettier or Biome to Oxfmt.
migrate-oxlint
Guide for migrating a project from ESLint to Oxlint. Use when asked to migrate, convert, or switch a JavaScript/TypeScript project's linter from ESLint to Oxlint.
insta-snapshots
Guide for working with and updating insta snapshot tests in Oxc without terminal interaction.
performance-lint-rules
Performance review guidance for Oxc linter rule implementations. Use only when reviewing Rust rule code under crates/oxclinter/src/rules/ or when explicitly auditing those rules for performance improvements.
oxc-docs
Comprehensive reference for the JavaScript Oxidation Compiler (Oxc) — a collection of high-performance JavaScript tools written in Rust. Covers parser design (lexer, AST, parser, errors, semantic analysis), architecture (parser, linter, test infrastructure, AST tools), ECMAScript specification and grammar, performance…
babel-docs
Babel 7.x/8.x — plugins, presets, config, @babel/core, parser, traverse, types, CLI, preset-env.