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.svg" alt="Measured on agentmods" 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.00041 | $0.04095 |
| Opus 5 | $0.00020 | $0.02048 |
| Sonnet 5 | $0.00008 | $0.00819 |
| Haiku 4.5 | $0.00004 | $0.00409 |
Grade A, and why
wrap scanned grade A with 1 finding 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 8d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
**Neo4j-first (connected mode only).** In connected mode, all queries via `bash bin/graph.sh query "..."`. No MCP. No direct curl to Neo4j. How it starts
The opening of the file, as written. The whole thing — 436 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Close your session with a personal summary. Saves everything.
Enriches the auto-captured Session node with topic, summary, and connections.
When to invoke
User says: "done", "wrapping up", "that's it", "let me wrap", "I'm done for now", "good stopping point", "call it a day", "wrap up", "wrap it"
Not this: "hand off to X" → /handoff · "push" or "keep working" → /save
Topic: $ARGUMENTS
Auto-saves. No need to run /save after.
Mode detection
MODE=$(jq -r '.mode // "connected"' egregore.json 2>/dev/null)
Local mode (mode === "local"): Skip ALL bin/graph.sh, bin/graph-op.sh, and bin/graph-wal.sh calls — do NOT run them. Do NOT show any graph-related messaging ("Graph offline", "will sync", Neo4j, Session node, enriched, etc.). Still call bin/capture-run.sh --mode personal; it writes and pushes the file-backed capture while automatically skipping graph reconciliation. Show a clear one-line confirmation (✓ Wrapped · memory/wraps/...). Skip all graph context queries, Artifact linking, and Session enrichment. The memory-side /save at the end still runs (git operations work the same in both modes).
Execution rules
Neo4j-first (connected mode only). In connected mode, all queries via bash bin/graph.sh query "...". No MCP. No direct curl to Neo4j.
Queue-first for writes (connected mode only). Foreground graph mutations
append to bin/graph-wal.sh; lifecycle reconciliation and network latency stay
in the detached worker.
CRITICAL: Suppress raw output. Never show raw JSON to the user. All bin/graph.sh and bin/graph-wal.sh calls MUST redirect stdout: pipe to /dev/null or capture in a variable. Only show formatted progress lines.
- 1 Bash call:
git config user.name - Session ID from
~/.egregore/session-{hash}.id - Git log + diff stat for context
- 3-5 Neo4j queries for context gathering
- 1-2 AskUserQuestion calls for validation + link suggestions
- Graph writes via WAL + direct
- Wrap file to
memory/wraps/YYYY-MM/ - Auto-save via
/saveflow - Telemetry emit
- TUI confirmation
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.
- 8d ago First seen · 436 lines · 41 tokens per session scan A 45f61fa3da03
wrap is a skill published in the GitHub repository egregore-labs/egregore (282 stars, last pushed 4d ago), licensed MIT. It adds 41 tokens to every session and 4,095 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
sw-handoff
Write a portable, secret-scrubbed handoff doc plus a diff of your uncommitted edits so another tool or machine resumes where you stopped. Use for "handoff", "out of tokens", "switch to Codex".
tokf-discover
Find missed token savings by scanning AI coding session files for commands that ran without tokf filtering.
handoff
Write a portable, secret-scrubbed handoff doc so this work can continue in any AI tool or on any machine. Use when saying "handoff", "running out of tokens", or "continue elsewhere".
claude-code-expert
Especialista profundo em Claude Code - CLI da Anthropic. Maximiza produtividade com atalhos, hooks, MCPs, configuracoes avancadas, workflows, CLAUDE.md, memoria, sub-agentes, permissoes e integracao com ecossistemas.
amq-spec
Use two agents to research a design independently and converge on one specification through AMQ. Trigger for collaborative design or messages labeled workflow:spec; use amq-cli for ordinary coordination.
notion-cli
Work with Notion from the terminal using the notion CLI. Use when the user needs to read, create, update, query, or manage Notion pages, databases, blocks, comments, users, or files programmatically. Covers the entire Notion API with 50+ commands. Triggers: Notion workspace automation, database queries, page creation…