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 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/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/onebrain-ai/onebrain/wrapup"><img src="https://agentmods.dev/badge/skills/onebrain-ai/onebrain/wrapup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Prompt Injection · line 145 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
- high Prompt Injection · line 348 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
- medium Agent Snooping · line 48 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Output Handling · line 502 Output size or generation rate is not bounded. Unbounded output enables denial-of-service through resource exhaustion, log flooding, or context-window stuffing.Fix: Set explicit limits on output length, generation count, and rate. Use max_tokens and truncation to prevent unbounded output.
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.00091 | $0.16204 |
| Opus 5.5 | $0.00036 | $0.06482 |
| Sonnet 5.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 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 — 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.
- 1mo ago First seen · 738 lines · 91 tokens per session scan A 415b2f225158
wrapup is a skill published in the GitHub repository onebrain-ai/onebrain (30 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 91 tokens to every session and 16,204 once invoked, about $0.0004 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
wrap-session-up
End-of-session review for a Claude Code conversation. Replays what was discussed, checks for open action items, documents relevant outcomes in the brain vault, and creates Todoist tasks for anything untracked. Use at the end of a work session to ensure nothing falls through the cracks.
vault-onboarding-guide
An interactive guide for learning a file-based knowledge store with an agent. It teaches how to organize incoming material, projects, plans, tasks, logs, parked work, and resumed work.
brain
Orient in the user's big-brain second brain and work brain-aware for the rest of the session. Use when the user types /brain, or asks "what am I working on", "what's on my plate", "catch me up", "what's overdue", or at the start of a session about ongoing work. Loads the vault overview, reports it in one screen, and…
obsidian-setup-consultant
Use this skill whenever the user wants to install, configure, migrate, design, or connect Obsidian as a second brain, knowledge base, cloud-synced vault, or AI/Hermes-readable memory. It is especially important when the user asks for an Obsidian setup prompt, vault architecture, folder structure, plugin…
obsidian-ai-setup
Bootstrap an Obsidian vault with the AI Pro Obsidian Plugin. Creates the complete vault structure, system files, Obsidian configuration, memory system, hooks, and output styles, then runs personalized onboarding to tailor the workspace to the user. Uses a single universal structure with no mode selection. Trigger when…
wiki-dashboard
Create dynamic, queryable Obsidian dashboard views using Bases or Dataview. Use for auto-updating tables, indexes, or structured views of vault content; not for ordinary question answering.