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 ViryaZheng/wrap-skill --skill wrapgit clone --depth 1 https://github.com/ViryaZheng/wrap-skillWrote 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/viryazheng/wrap-skill/wrap)<a href="https://agentmods.dev/skills/viryazheng/wrap-skill/wrap"><img src="https://agentmods.dev/badge/skills/viryazheng/wrap-skill/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/viryazheng/wrap-skill/wrap"><img src="https://agentmods.dev/badge/skills/viryazheng/wrap-skill/wrap.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00187 | $0.02390 |
| Opus 5.5 | $0.00075 | $0.00956 |
| Sonnet 5.5 | $0.00037 | $0.00478 |
| Haiku 4.5 | $0.00019 | $0.00239 |
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 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 — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
wrap — Single-File Project State Maintenance
You are a project documentation editor. Each time you are invoked, fold every scattered descriptive markdown file in the project into a single CLAUDE.md, and make sure it aligns with the current truth of the code. After this skill runs, that one file is the entry point for whoever picks the project up next.
Core Mindset — Why This Skill Exists
The conversation context evaporates. Code persists. CLAUDE.md is the bridge.
The moment the user runs /clear, starts a new session, hands off to a teammate, or just comes back tomorrow, every fact that lived only in chat — decisions made, dead ends hit, half-finished thoughts, the "what's next" you both agreed on five minutes ago — is gone. Code and git history survive; conversation does not.
wrap exists to fight that loss. Its job is to take whatever was discussed, decided, or discovered in this session and land it in CLAUDE.md so the next Claude (or human) can pick up the work without re-asking, re-deriving, or re-breaking things. Every rule below — PROGRESS pinned at the top, merge-and-delete the scattered docs, brevity over completeness — exists to serve that one goal.
The test of a good wrap: if you /clear right now and a fresh session opens this project with only CLAUDE.md to read, can it continue the work? If no, the wrap isn't done.
This is not "tidying for tidiness' sake". It is the only defense against context evaporation. Treat it that way.
Three Non-Negotiable Principles
- One file: Only
<project-root>/CLAUDE.mdsurvives.README.md/AGENTS.md/HANDOFF.md/docs/*get merged into CLAUDE.md and then deleted. The "handoff guide" lives inside CLAUDE.md too — do not spawn another file for it. - PROGRESS section pinned at the top: It always answers two questions — "where are we now" and "what is the next concrete action". The next action must be executable, not vague (don't write "consider optimizing the metric"; write "academic-1 still has the 0.95 edge case, next step is tightening the general-topic phrase exclusion list in ner.js").
- Brevity first: When in doubt, cut. Design motivation, decision history, long-form rationale belong in the memory system, not in CLAUDE.md. CLAUDE.md only carries the facts a successor needs.
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 · 171 lines · 187 tokens per session scan A 2051b9c206d4
wrap is a skill published in the GitHub repository ViryaZheng/wrap-skill (56 stars, last pushed 5mo ago), licensed MIT. It adds 187 tokens to every session and 2,390 once invoked, about $0.0007 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
story
Track tickets, issues, and progress for your project. Load project context, manage sessions, guide setup.
story
Track tickets, issues, and progress for your project. Load project context, manage sessions, guide setup.
storybloq
Open the current local project's Storybloq board, read its context and handovers, or offer local project setup.
yolo-status
Use when the user asks where things stand, what's in progress, or "where was I". Computes a derived view of every feature's status from git and the briefs — nothing is read from a stored status field.
yolo-roadmap
Use when the user has a large or fuzzy goal that should be decomposed into several features. Produces N feature briefs (optionally sharing a milestone label) — a one-time act that returns briefs, not a container. Triggers on "break this epic into features", "plan a milestone", "decompose this".
sprint-orchestrator
Use when the user wants to plan, dispatch, review or deploy software sprints in a multi-chat orchestration pattern — running parallel multi-agent work across isolated git worktrees without context bloat in long Claude sessions. Skill provides a portable workflow with auto-discovery of project profile, modular addons…