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/olelehmann1337/ole-plugins/setupnpx skills add olelehmann1337/ole-plugins --skill setupgit clone --depth 1 https://github.com/olelehmann1337/ole-pluginsWhat 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.00101 | $0.02799 |
| Opus 5 | $0.00051 | $0.01399 |
| Sonnet 5 | $0.00020 | $0.00560 |
| Haiku 4.5 | $0.00010 | $0.00280 |
Grade C, and why
setup scanned grade C with 2 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
[ -f ~/.claude/CLAUDE.md ] && cat ~/.claude/CLAUDE.md Enumerates other installed skillsmediumAgent snooping
Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.
ls -d ~/.claude/skills/*brand* ~/.claude/skills/*voice* 2>/dev/null How it starts
The opening of the file, as written. The whole thing — 265 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Second Brain — Setup
USE WHEN the user runs /setup or asks to set up their vault, bootstrap the assistant, or initialize their second brain.
The Goal
Get the user from zero to a working second brain in under five minutes. No technical dependencies. No plugins to install. No API keys to configure. Just a folder, a vault, and Claude.
Three Phases
- Phase 0 — Context Scan. Silently pull everything we can from existing Claude context, skills, and local markdown. Don't ask yet — gather first.
- Phase A — Bootstrap. Create the folder structure and write system files.
- Phase B — Onboarding. Ask for a website URL, scrape it for voice and ICP signals, generate draft Context files, show them for approval.
Pre-flight Check
Check if claude.md or CLAUDE.md exists in the current working directory. Check only the exact CWD — don't search subdirectories or parents.
- If it exists: this vault is already set up. Ask the user:
- Re-run onboarding — Keep the existing structure, regenerate the Context files from fresh inputs.
- Full reset — Delete everything and start fresh. Confirm twice before proceeding.
- Cancel — Stop here.
- If it does NOT exist: proceed to Phase 0.
Phase 0: Context Scan (silent, fast)
Before asking the user anything, pull as much useful context as possible from the machine. Run these checks silently — no narration, no questions yet.
Scan Targets
Run each of these and collect the text. Don't block on failures — missing files are normal.
1. Global Claude context:
[ -f ~/.claude/CLAUDE.md ] && cat ~/.claude/CLAUDE.md
2. Current directory and close parents:
[ -f ./CLAUDE.md ] && cat ./CLAUDE.md
[ -f ../CLAUDE.md ] && cat ../CLAUDE.md
[ -f ../../CLAUDE.md ] && cat ../../CLAUDE.md
3. Brand / voice / ICP files nearby:
find . -maxdepth 2 -type f -iname "*.md" | xargs grep -l -i -E "(brand|voice|icp|about|bio|tone)" 2>/dev/null | head -5
Read the top few matches.
What ships with it
13 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.
- references/claude-md-template.md 8.5 KB
- references/claudeignore-template.md 41 B
- references/context-business.md 456 B
- references/context-icp.md 905 B
- references/context-strategy.md 666 B
- references/context-voice.md 651 B
- references/gitignore-template.md 211 B
- references/guide-context.md 669 B
- references/guide-daily.md 692 B
- references/guide-projects.md 807 B
- references/guide-resources.md 963 B
- references/guide-skills.md 805 B
- references/settings-json-template.md 136 B
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 · 265 lines · 101 tokens per session scan C 86125068f7ce
setup is a skill published in the GitHub repository olelehmann1337/ole-plugins (8 stars, last pushed 4mo ago), licensed MIT. It adds 101 tokens to every session and 2,799 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it C with 2 findings (reads agent configuration directories, enumerates other installed skills). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
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…