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/auerbachb/claude-code-config/wrapnpx skills add auerbachb/claude-code-config --skill wrapgit clone --depth 1 https://github.com/auerbachb/claude-code-configWhat 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.00052 | $0.18570 |
| Opus 5 | $0.00026 | $0.09285 |
| Sonnet 5 | $0.00010 | $0.03714 |
| Haiku 4.5 | $0.00005 | $0.01857 |
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 2d 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 — 972 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wrap up the current PR and session. This is the "we're done here" command that handles final verification through merge, root-main sync, follow-up detection, a full-session sweep for loose ends, and lessons.
/wrap accepts an optional PR reference as its argument — a full URL, #N, owner/repo#N, or a bare number N. When invoked with no argument it resolves the target PR through the inference cascade in Step 1.1 (current branch → thread context → session-state). An explicit argument bypasses all inference.
/wrap does not delete the running worktree or its branch — leaving the thread alive so it can keep working. Stale worktrees and stale local/remote branches are reaped out-of-band by /pm-update, which calls stale-cleanup.sh.
When to use /wrap vs /merge
- Use /wrap at end-of-session. Handles merge + root-main sync + follow-up detection + lessons.
- Use /merge for a quick mid-session merge when you'll keep working. Skips follow-up detection and lessons.
- /wrap includes everything /merge does, plus follow-ups and lessons. Don't run both.
- Phase C invokes this skill after gate and AC verification; keep merge, main-sync, follow-up, and cleanup behavior here so Phase C and
/wrapcannot drift. - Target PR:
/wrapoperates on the PR resolved in Step 1.1. Pass an explicit reference (/wrap <URL>,/wrap #N,/wrap N) to wrap a PR that is not on the current branch — common in orchestration threads that ran/fixpr <URL>against another worktree. With no argument, Step 1.1's cascade infers the PR. - Callers of the
/wrap #Nform: Phase C (phase-c-merger),/pr-monitor-and-manage(merge-ready fleet PRs), and/pm's one-shot forgotten-PR triage (issue #657) all merge an already-open PR by dispatching this workflow rather than reimplementing merge logic — the merge gate, AC verification, and squash-merge live here so every caller stays consistent.
Execution Model
/wrap is a set-and-forget command. Once invoked, it runs all 4 phases end-to-end without mid-run confirmation prompts. It stops early only for explicit stop conditions (for example: no PR on current branch, human change requests on HEAD, recovery iteration cap, failed merge gate after recovery, /fixpr delegation failure, AC verification failure).
What ships with it
3 files 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.
- 2d ago First seen · 972 lines · 52 tokens per session scan A 28b2a1e1fdd3
wrap is a skill published in the GitHub repository auerbachb/claude-code-config (5 stars, last pushed 2d ago), licensed MIT. It adds 52 tokens to every session and 18,570 once invoked, about $0.0003 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
author-product-docs
Create, revise, retrofit, audit, or verify product documentation — pack READMEs, journeys, tutorials, how-to guides, reference pages, and explanations. Use when asked to write, improve, restructure, audit, or verify user-facing documentation, fix a pack README, create a guide for a feature, update a journey page, or…
exam
Examine the human on the code they are about to push. Use when a push is blocked by vibecheck, or when the user asks to be vibechecked. Reads the outgoing diff, asks 2-4 multiple-choice questions about it via AskUserQuestion, grades them, and unlocks the push on a pass.
harness
Cybernetics-based multi-agent orchestration for complex tasks. Coordinates a Planner → Generator → Evaluator → Retro pipeline with clean-context sub-agents, per-checkpoint drift prevention, and persistent retro learning. Recommended workflow: Claude Code plans the spec (Session 1), Codex executes autonomously (Session…
sparda-mcp
Drive a SPARDA compiled Behavior Runtime to its full potential. Use this whenever you are connected to a backend running the SPARDA Runtime (compiled into a Unified Behavior Graph - UBG) — recognizable by the tools spardagetcontext, spardainfo, spardaconfirm, or composite tools. It teaches the graph-context-first…
sparda-mcp
Drive a SPARDA compiled Behavior Runtime to its full potential. Use this whenever you are connected to a backend running the SPARDA Runtime (compiled into a Unified Behavior Graph - UBG) — recognizable by the tools spardagetcontext, spardainfo, spardaconfirm, or composite tools. It teaches the graph-context-first…
article-writing
Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.