Borrowing it
Nothing to install: this file belongs to egregore-labs/egregore. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/egregore-labs/egregore/main/.claude/skills/wrap/SKILL.mdgit clone --depth 1 https://github.com/egregore-labs/egregoreWrote 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/egregore-labs/egregore/wrap)<a href="https://agentmods.dev/skills/egregore-labs/egregore/wrap"><img src="https://agentmods.dev/badge/skills/egregore-labs/egregore/wrap/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/egregore-labs/egregore/wrap"><img src="https://agentmods.dev/badge/skills/egregore-labs/egregore/wrap.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.00058 | $0.00866 |
| Opus 5.5 | $0.00023 | $0.00346 |
| Sonnet 5.5 | $0.00012 | $0.00173 |
| Haiku 4.5 | $0.00006 | $0.00087 |
Grade A, and why
wrap 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 24d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Personal session wrap
Record what this actor finished, what was verified, and what remains. A wrap is personal session closure, not a handoff, notification, publication, or claim that an organizational obligation is complete.
Canonical Markdown and Git provenance are authoritative. The Egregore Runtime owns authorization, stable ActorContext resolution, persistence, provenance, retrieval refresh, background embedding, and content-free telemetry through one writeback transaction.
When to invoke
Close the current Egregore session with a personal, canonical summary. Use for /wrap or when the user says they are done, wrapping up, or at a stopping point. Route work assigned to another person to /handoff and save-without-closing to /save.
Prepare
- Reuse the current conversation and relevant
EGREGORE_ORG_CONTEXT_V1evidence. Do not search organizational memory again merely to summarize the session. - Derive a short topic, a two-to-four sentence summary, verified outcomes, and concise open threads. Separate completed work from unverified work.
- If the proposed summary is materially ambiguous, show it once and ask for correction. Skip confirmation when the user already supplied exact wrap wording.
- If project changes need delivery, invoke
/saveonce before the wrap. That is a separate project-delivery action; do not reproduce Git commands in this skill and do not run a second save after canonical wrap succeeds.
Use this body shape, omitting empty sections:
## Summary
<what changed and the current state>
## Completed
- <completed outcome>
## Verification
- <test or check and its result>
## Open Threads
- [ ] <unfinished item or next step>
Write once
Write this body to the file tmp/wrap-body.md, then pass it to
the Runtime-neutral wrap adapter in one command:
<body markdown>
Use {topic} for the short topic and {summary} for the two-to-four sentence summary
derived from the session during preparation:
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.
- 24d ago Changed · -332 lines · +17 tokens per session 6871c03082d7
- 1mo ago First seen · 436 lines · 41 tokens per session scan A 45f61fa3da03
wrap is a skill published in the GitHub repository egregore-labs/egregore (293 stars, last pushed 9d ago), licensed MIT. It adds 58 tokens to every session and 866 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
batch-api
Prepare a many-file, single-turn transform (translate, rewrite, extract) as a plan and submit it to the asynchronous, half-price DashScope Batch API; results are delivered as new files hours later. Invoke explicitly with /batch-api.
gws-calendar
Google Calendar: Manage calendars and events.
gws-gmail-send
Skill "gws-gmail-send" from googleworkspace/cli, covering gmail +send, usage, flags, examples and tips.
obsidian-bases
Create and edit Obsidian Bases (.base files) with views, filters, formulas, and summaries. Use when working with .base files, creating database-like views of notes, or when the user mentions Bases, table views, card views, filters, or formulas in Obsidian.
gws-gmail-watch
Gmail: Watch for new emails and stream them as NDJSON.
gws-gmail
Gmail: Send, read, and manage email.