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/verifynpx skills add Eigenwise/eigenwise-toolshed --skill verifygit 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.00001 | $0.00486 |
| Opus 5 | $0.00000 | $0.00243 |
| Sonnet 5 | $0.00000 | $0.00097 |
| Haiku 4.5 | $0.00000 | $0.00049 |
Grade B, and why
verify 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.
3. `ensure --quiet` with a temporary `~/.claude/settings.json` containing legacy settings. The command may exit nonzero when no proxy binary exists; inspect the settings mutation itself. What it actually says
Verify model-gateway
Use an isolated temporary home and random localhost ports. Start bin/model-gateway.js serve-shim against a tiny fake HTTP proxy that serves /v1/models and records forwarded message bodies.
Drive these surfaces:
GET /v1/modelsthrough the running shim.POST /v1/messagesusing both current and legacy model IDs, then inspect the fake proxy's received model.ensure --quietwith a temporary~/.claude/settings.jsoncontaining legacy settings. The command may exit nonzero when no proxy binary exists; inspect the settings mutation itself.env --write-projectagainst a temporary project directory to check that wiring lands in that project's.claude/settings.local.jsonand never in a committed.claude/settings.json. Thenenv --write-useragainst a temporary HOME for the shared fallback, checking preservation of user-set values. With both set,doctormust name the project-local one as effective and fail a mode contradiction.--modeand--show-modeare retired and must exit 2.- RC-compatibility mode: set
CODEX_GATEWAY_HOSTS_FILEto a temp hosts file andCODEX_GATEWAY_COMPAT_PORTto a free ephemeral port (never the real 80) before startingserve-shim. With the file containing127.0.0.1 api.anthropic.com,GET /healthzon both the main port and the compat port must reportcompat.hostsDetected: trueandcompat.port80Bound: true. With the entry absent, both must be false and the compat port must refuse connections. Pre-binding the compat port before spawning the shim proves the safe fallback:hostsDetected: true,port80Bound: false, a populatedreason, and the main port still serving normally. - DNS-recursion guard: require
lib/request-worker.jsdirectly and callcreateHostsBypassResolver({ resolve4, resolve6 })with injected fake resolvers to confirm it never falls back to a hosts-aware lookup and errors closed when both resolvers fail.
Keep the real gateway and user settings untouched. Capture response bodies and resulting settings JSON inline.
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 · 20 lines · 1 tokens per session scan B 0f91c54006c6
verify is a skill published in the GitHub repository Eigenwise/eigenwise-toolshed (36 stars, last pushed 4d ago), licensed MIT. It adds 1 tokens to every session and 486 once invoked, about $0.0000 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…
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.