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/onebrain-ai/onebrain/wrapupnpx skills add onebrain-ai/onebrain --skill wrapupgit clone --depth 1 https://github.com/onebrain-ai/onebrainWrote 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/onebrain-ai/onebrain/wrapup)<a href="https://agentmods.dev/skills/onebrain-ai/onebrain/wrapup"><img src="https://agentmods.dev/badge/skills/onebrain-ai/onebrain/wrapup.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.00091 | $0.16204 |
| Opus 5 | $0.00046 | $0.08102 |
| Sonnet 5 | $0.00018 | $0.03241 |
| Haiku 4.5 | $0.00009 | $0.01620 |
Grade A, and why
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 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.
How it starts
The opening of the file, as written. The whole thing — 738 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session Summary (TL;DR)
Generates a summary of this session and saves it to the logs folder for future recall.
Scope
/wrapup writes the session log only. It does NOT promote insights to memory/ — that is /recap's responsibility. Do not write to MEMORY.md or memory/ files.
Session Log Frontmatter
See skills/startup/references/session-formats.md → Session Log Format for frontmatter variants and body sections. Never add recapped: or topics: — those are populated by /recap later.
Step 0: Active Pause Thread Detection
Run this BEFORE Step 1.
-
Read
[logs_folder]/pause/_active.md. If absent or empty → setwrapup_mode = "session"; skip to Step 1 (zero-overhead path for non-pause sessions). -
If a slug is present: parse the file's single-line content as
slug. Glob[logs_folder]/pause/*-{slug}-pause-*.md→pause_count(file count) and derivefirst_date= earliestYYYY-MM-DDdate prefix among matched files (used in Step 3's question text). -
Use
AskUserQuestion:Question: "Active pause thread:
{slug}({pause_count} snapshots since {first_date}). Wrap up this thread now?" Options:- "Yes — consolidate into one session log" (sets
wrapup_mode = "thread") - "No — wrapup today's work only; keep pause thread active" (sets
wrapup_mode = "session")
- "Yes — consolidate into one session log" (sets
-
If
wrapup_mode = "session"AND active pause exists → fall through to Step 0b: Auto-Finalize Pause (below) BEFORE proceeding to Step 1. -
If
wrapup_mode = "thread"→ proceed to Step 1 normally, then branch in Step 4 (see Step 4 modifications below).
Step 0b: Auto-Finalize Pause (Session-mode wrapup with active thread)
Runs only when wrapup_mode = "session" AND _active.md exists.
Apply the four skip conditions from skills/pause/SKILL.md → Auto-Finalize section:
- No-activity: if no checkpoint file exists for current
session_token, skip Auto-Finalize. - Already-captured-this-session: if latest pause file's frontmatter
session_tokenmatches current AND no checkpoint mtime > pause file mtime, skip. - No-pause-files-and-untouched: if no pause file exists for slug AND newest checkpoint mtime <
_active.mdmtime, skip. - Thread-untouched: if this session did no work on the thread after the thread's latest pause file was written (ALL of: no
/resumeof this slug after that point AND no thread-related checkpoint/conversation content after it — judge from checkpoint files, which survive compaction), skip — auto-finalizing would append unrelated work into the thread. A session that resumed or continued the thread does NOT match.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 738 lines · 91 tokens per session scan A 415b2f225158
wrapup is a skill published in the GitHub repository onebrain-ai/onebrain (25 stars, last pushed 6d ago), licensed Apache-2.0. It adds 91 tokens to every session and 16,204 once invoked, about $0.0005 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
llm-wiki
Build and maintain a persistent, interlinked Obsidian-compatible markdown wiki using Karpathy's LLM Wiki pattern. Extension-backed with auto-generated metadata, guardrails, and 14 custom tools (+3 opt-in agent-trajectory tools).
link-memory
Use after important user-approved decisions, when durable context should be proposed or reviewed, and for explicit Link memory lifecycle work: remember, recall, review, update, archive, restore, forget, or explain local memories through the CLI without requiring MCP.
link-retrieve
Use before answering work that may depend on user memory, project history, source-backed notes, or prior decisions; retrieve compact Link context through the CLI without loading the whole wiki or requiring MCP.
link-ingest
Use when raw files are present, source pages look stale, or a user asks to ingest notes into Link; refresh source-backed wiki pages, propose memories, and validate updates through the CLI without MCP.
lint-brain
Run health checks over the brain vault - find orphan notes, broken wikilinks, missing frontmatter, stale projects, and missing cross-links. Use when asked to "lint the brain", "health check", "vault hygiene", or "/lint-brain".
ingest-article
Ingest an article from a URL or raw text into the brain vault. Extracts key knowledge, determines placement, creates or updates notes, and links to relevant projects. Use when the user shares a URL or text and wants to absorb it into their knowledge base.