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/eigenwise/eigenwise-toolshed/setupnpx skills add Eigenwise/eigenwise-toolshed --skill setupgit clone --depth 1 https://github.com/Eigenwise/eigenwise-toolshedWhat 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.00104 | $0.02448 |
| Opus 5 | $0.00052 | $0.01224 |
| Sonnet 5 | $0.00021 | $0.00490 |
| Haiku 4.5 | $0.00010 | $0.00245 |
Grade B, and why
setup scanned grade B 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
install and write list (every file path, including any `~/.claude/settings.json` change) and get How it starts
The opening of the file, as written. The whole thing — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quartermaster setup
Outfit a project's .claude/ workspace end to end. You are an orchestrator: the pieces already
exist (codebase-mapper's map-codebase, live-rules' add-rule, sidequest, observability's
enable-project-telemetry, model-gateway, the built-in /init). Your job is to ground the plan
in the user's actual history, interview briefly, install in the right order around the plugin
reload boundary, and verify the result really works.
What makes this different from a checklist bootstrap: recommendations come from evidence. The miner shows which plugins the user leans on across projects, which permission denials repeat, and which corrections they keep giving. A new project starts where the others left off.
Process
1. Assess the project
Read the obvious markers in the project root (package.json, pyproject.toml, Cargo.toml, go.mod,
existing CLAUDE.md, existing .claude/). Establish:
- New vs existing: real source files vs empty scaffold.
- Codebase vs not: a wiki or notes vault skips the codebase map but may still want live-rules and sidequest.
- What is already there: an existing
.claude/means augmenting, never clobbering. Read it first, merge, and say what you will add and what you will leave alone. - Git: if not a repo, ask once whether to
git init(recommended: it preserves the setup); respect a no.
2. Mine the user's history
node "${CLAUDE_PLUGIN_ROOT}/bin/quartermaster.js" mine --all-projects --days 45 --sessions 60
This is the cross-project view: attribution shows which plugins and MCP servers the user
actually uses; denial patterns show which permissions to pre-allow; correction themes show which
rules to seed. Also run node "${CLAUDE_PLUGIN_ROOT}/bin/quartermaster.js" catalog --installed
to see what user-scope plugins already apply here.
3. Interview, briefly
Ask what the project is for (one or two lines), confirm the detected stack, and ask team-or-solo plus any conventions worth encoding. Propose defaults from the assessment and the mining so the user confirms rather than types essays. Every question carries one sentence on why the answer matters.
What ships with it
5 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 · 179 lines · 104 tokens per session scan B 23c6b177ff57
setup is a skill published in the GitHub repository Eigenwise/eigenwise-toolshed (36 stars, last pushed 4d ago), licensed MIT. It adds 104 tokens to every session and 2,448 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). 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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…