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/nullphase-net/enfurbish/wrapnpx skills add nullphase-net/enfurbish --skill wrapgit clone --depth 1 https://github.com/nullphase-net/enfurbishWrote 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/nullphase-net/enfurbish/wrap)<a href="https://agentmods.dev/skills/nullphase-net/enfurbish/wrap"><img src="https://agentmods.dev/badge/skills/nullphase-net/enfurbish/wrap.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.00072 | $0.03866 |
| Opus 5 | $0.00036 | $0.01933 |
| Sonnet 5 | $0.00014 | $0.00773 |
| Haiku 4.5 | $0.00007 | $0.00387 |
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 3d 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 — 278 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/wrap — Session-end retrospective
Run this at the end of a session. It captures what was learned, evaluates how the user's tooling stack performed, and stages the next session.
Modes
/wrap with no args does everything below.
/wrap -q (or --quick) does only the local repo work — the NEXT_SESSION.md lifecycle (step 5) and any CLAUDE.md routing (step 6). It skips the retro file (step 3) and the journal append (step 4), the two writes that land outside the repo. Step 1 still runs: scan.ts is a read, and step 5 needs session_start and files_edited from it. Step 2 is skipped along with the journal.
Use it when the session's value is a clean pointer, not a retrospective — a short arc, a mid-day handoff, a session whose tooling story is identical to the last one you journaled.
What you produce
- Dated retro file at
~/.claude/sessions/YYYY-MM-DD-<cwd-slug>-<sessionid8>.md— the canonical record. (skipped under-q) - Tooling journal entry appended to
~/.claude/tooling-journal.mdviajournal-append.ts. (skipped under-q) NEXT_SESSION.mdat the project root — written, left alone, or removed per the lifecycle rules below.- (Conditional) CLAUDE.md edits — user-level or project-level, only with explicit user confirmation.
Procedure
1. Run scan.ts
The skill's lib scripts live at the plugin root, two levels up from this SKILL.md. Use the base directory Claude told you about for this skill:
bun run "<skill-base-dir>/../../lib/scan.ts" --cwd "$(pwd)"
Parse the JSON. If ok: false, note degraded: true, reason: "..." and proceed with self-reported stats from your own session memory.
Buffering note: Claude Code may buffer transcript writes, so the last few events (including the /wrap call itself) may not appear in the count. If session_end from scan.ts is more than ~60s behind the current wall-clock time, mention "stats trail by ~Ns" in the journal entry under the relevant tool — otherwise the count silently undercounts.
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.
- 3d ago First seen · 278 lines · 72 tokens per session scan A 728e3ff0a74d
wrap is a skill published in the GitHub repository nullphase-net/enfurbish (1 stars, last pushed 16d ago), licensed MIT. It adds 72 tokens to every session and 3,866 once invoked, about $0.0004 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-31.
Other skills, from other repositories
context-guard
Installs Claude Code hooks that keep AI context files fresh. Two-tier enforcement — Tier 1 nudges at session end, Tier 2 blocks commits when structural files are staged without context updates. Includes content filter, drift check, structural change reminder, SessionStart health check, and the context-updater agent.
context-verify
Validates AI context file quality with 16 checks and 0-100 health scoring. Works on any platform — also available as a standalone CLI script (bin/context-verify.sh). Validates line budgets, AGENTS-to-bridge consistency, stale paths, MEMORY.md drift, plugin manifest, and modern Cursor (.cursor/rules/.mdc) / Cline…
contextdocs
Your AI agent maintains its own context files — a Claude Code plugin with an AGENTS-first model that covers Codex, Copilot, Cursor, Gemini, and 3 more tools. Signal Gate filtering, Context Guard hooks, health scoring, and MEMORY.md promotion.
ai-context
Generates, updates, and audits AGENTS-first AI IDE context files. Builds canonical AGENTS.md plus thin bridges for Claude Code, Cursor (modern .cursor/rules/.mdc), Copilot, Cline (.clinerules/ directory), Windsurf, Gemini CLI, Codex CLI, and OpenCode. Use for creating, regenerating, fixing, or promoting context files…
repo-indexer
Indexes and documents a codebase for persistent Claude context with minimal token overhead. Use when asked to index a repo, understand a codebase, create CLAUDE.md, set up Claude memory, bootstrap context, onboard to a project, or document codebase for Claude. Triggers on phrases like "index this repo", "understand…
memory-recall
Search and recall relevant memories from past sessions via memsearch. Use when the user's question could benefit from historical context, past decisions, debugging notes, previous conversations, or project knowledge -- especially questions like 'what did I decide about X', 'why did we do Y', or 'have I seen this…