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/leejuoh/claude-code-zero/setup-aliasesnpx skills add LeeJuOh/claude-code-zero --skill setup-aliasesgit clone --depth 1 https://github.com/LeeJuOh/claude-code-zeroWhat 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.00059 | $0.06395 |
| Opus 5 | $0.00030 | $0.03197 |
| Sonnet 5 | $0.00012 | $0.01279 |
| Haiku 4.5 | $0.00006 | $0.00639 |
Grade A, and why
setup-aliases scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Bash(curl *) How it starts
The opening of the file, as written. The whole thing — 318 lines — stays where its author put it; the contents beside it link to each section on GitHub.
setup-aliases
State-aware orchestration for VibeProxy aliases. This skill owns exactly two surfaces:
- the
vibeproxy-kitmanaged block in~/.zshrc - the
oauth-model-aliasentries in~/.cli-proxy-api/config.yamlthat it created
Everything else — unrelated YAML keys, unrelated shell aliases, user-authored alias entries — is preserved. The skill coordinates discovery, a guided per-backend probe cycle, writes, a VibeProxy restart gate, live validation, and transactional rollback on failure.
All five scripts in ${CLAUDE_PLUGIN_ROOT}/skills/setup-aliases/scripts/ emit JSON to stdout. Your job is to chain them together, surface decisions to the user via AskUserQuestion, and persist state to ${CLAUDE_PLUGIN_DATA}/config.json before any write.
Phase 1 — Discover
Run the read-only inspector and parse its JSON:
bash ${CLAUDE_PLUGIN_ROOT}/skills/setup-aliases/scripts/discover.sh > /tmp/vibeproxy_discover.json
Then read /tmp/vibeproxy_discover.json. Key fields:
vibeproxy_installed,vibeproxy_reachable— see Onboarding gates below if either is falseuser_overlay_exists,state_file_present— determines whether we are first-run or rerunauthenticated_backends— array of{token, config_key, display_name, auth_files}; see Onboarding gates below if empty or missing backends the user wantsclaude_code_channel—{connected, account_count}; see Claude Code channel note belowmanaged_shell_aliases,managed_model_aliases,managed_payload_overrides,shortcut_shell_aliases— what the skill currently ownsbackend_catalogs,partial_probe— cached probe results and any aborted probe cycleconflicts— pre-existingcc-*entries that are not tracked in state (potential clashes); includesmanual-shell-alias,manual-config-alias:<channel>, andmanual-payload-override:<protocol>sources
Present a compact summary back to the user (do not dump raw JSON):
VibeProxy: installed ✓ | reachable ✓
Authenticated backends: codex, copilot, gravity, gemini (4/4)
Claude Code channel: not connected
Currently managed: 3 model aliases, 4 shell aliases, 1 shortcut
Manual conflicts detected: 0
State file: present (last probe 2 days ago)
What ships with it
8 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/effort-levels.md 2.5 KB
- references/model-selection.md 9.1 KB
- references/write-guide.md 4.1 KB
- scripts/discover.sh 13 KB runs code
- scripts/probe_backend.sh 2.5 KB runs code
- scripts/verify_probe.py 13 KB runs code
- scripts/write_user_config.py 14 KB runs code
- scripts/write_zshrc.sh 9.1 KB runs code
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 · 318 lines · 59 tokens per session scan A 7d49522d656c
setup-aliases is a skill published in the GitHub repository LeeJuOh/claude-code-zero (51 stars, last pushed 2d ago), licensed MIT. It adds 59 tokens to every session and 6,395 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.