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/neurofoo/agent-skills/wrapnpx skills add neurofoo/agent-skills --skill wrapgit clone --depth 1 https://github.com/neurofoo/agent-skillsWrote 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/neurofoo/agent-skills/wrap)<a href="https://agentmods.dev/skills/neurofoo/agent-skills/wrap"><img src="https://agentmods.dev/badge/skills/neurofoo/agent-skills/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.00037 | $0.00794 |
| Opus 5 | $0.00018 | $0.00397 |
| Sonnet 5 | $0.00007 | $0.00159 |
| Haiku 4.5 | $0.00004 | $0.00079 |
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 4d 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WRAP Decision Framework
Apply the complete WRAP framework to make a better decision by countering the four villains of decision-making.
Instructions
Work through all four phases sequentially. Each phase targets a specific cognitive bias that undermines good decisions.
Output Format
Decision: [What are we deciding?] Context: [Key constraints and stakes]
W: WIDEN Your Options
Counter: Narrow Framing ("Should I do X?" → "What are all my options?")
Current Framing How is the decision currently framed? (Often as "whether or not")
Expanded Options
| # | Option | Why It's Worth Considering |
|---|---|---|
| 1 | [option] | [rationale] |
| 2 | [option] | [rationale] |
| 3 | [option] | [rationale] |
| 4 | [option] | [rationale] |
Option-Finding Techniques
- Vanishing options test: "If you couldn't do X, what would you do?"
- Opportunity cost: "What else could you do with this time/money?"
- Find someone who solved it: "Who's had this problem?"
R: REALITY-TEST Your Assumptions
Counter: Confirmation Bias (seeking evidence that confirms what we want)
Key Assumptions
| Assumption | How Would We Know If Wrong? |
|---|---|
| [assumption 1] | [test] |
| [assumption 2] | [test] |
Consider the Opposite For each option, what would it take to be convinced it's wrong?
Ooch Is there a small experiment we can run to test this before fully committing?
| Option | Small Test | What We'd Learn |
|---|---|---|
| [option] | [test] | [insight] |
A: ATTAIN Distance Before Deciding
Counter: Short-term Emotion (deciding when angry, excited, or desperate)
10/10/10
| Time Horizon | How will you feel about this decision? |
|---|---|
| 10 minutes | [how you feel now] |
| 10 months | [how you'll likely feel] |
| 10 years | [long-term perspective] |
What Would I Tell My Best Friend? If someone you loved faced this decision, what would you tell them?
What ships with it
6 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.
- 4d ago First seen · 123 lines · 37 tokens per session scan A c9629d6c6615
wrap is a skill published in the GitHub repository neurofoo/agent-skills (111 stars, last pushed 7mo ago), licensed MIT. It adds 37 tokens to every session and 794 once invoked, about $0.0002 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…