A guide for repairing a tool's environment when its setup or installation fails.

It helps eject a tool's setup into an editable folder, enable detailed setup output, patch setup files, and configure the tool to use the patched copy.

It explains how to diagnose setup errors and apply a fix locally or prepare a fix for the project itself.

How evo-design/proto-tools configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to evo-design/proto-tools. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/evo-design/proto-tools/main/.claude/skills/fix-env/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/evo-design/proto-tools

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/evo-design/proto-tools/fix-env/github.svg)](https://agentmods.dev/skills/evo-design/proto-tools/fix-env)

Your own site

<a href="https://agentmods.dev/skills/evo-design/proto-tools/fix-env"><img src="https://agentmods.dev/badge/skills/evo-design/proto-tools/fix-env/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/evo-design/proto-tools/fix-env"><img src="https://agentmods.dev/badge/skills/evo-design/proto-tools/fix-env.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 202 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,541 The whole file, excluding the scripts and references it only reads on demand.

Security scan C 1 finding. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.1	$0.00202	$0.02541
Opus 5.5	$0.00081	$0.01016
Sonnet 5.5	$0.00040	$0.00508
Haiku 4.5	$0.00020	$0.00254

Measured 1mo ago against content hash de1dfcf44682, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade C, and why

fix-env scanned grade C 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 1mo 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

rm -rf tool_envs/{tool}_env

.claude/skills/fix-env/SKILL.md · 170 lines

How it starts

The opening of the file, as written. The whole thing — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.

fix-env

When to use: a tool's environment fails to build or work, and you need to fix it — either just on the current machine, or as a fix the whole project should ship.

Two ways to fix an env

The diagnosis is identical; what differs is where you apply the fix and how compatible it has to be. Decide the mode first; the failure patterns and workflow below apply to both.

Local fix — "I just need this tool working on my machine"

For when you (or a user you're helping) hit a broken env and want it working now, without modifying the installed package. Works for any install, including a non-editable pip install where the packaged files sit in read-only site-packages.

Eject the tool's setup into an editable copy and set the variable it prints:

proto-tools eject-standalone <toolkit>          # -> ./proto_standalone/<toolkit>/
export PROTO_<TOOLKIT>_STANDALONE_DIR=$PWD/proto_standalone/<toolkit>

See the failure live by re-running the tool with PROTO_ENV_VERBOSE=1 (streams setup.sh output to your terminal); diagnose with the patterns below.
Patch the ejected files (setup.sh, etc.) under ./proto_standalone/<toolkit>/.
Rebuild by re-running the tool — with the variable set, the next call builds from your copy under an isolated env name. Iterate until it runs.

Never edit the installed package. Tell the user to export the variable per project (e.g. a direnv .envrc) so it applies only where they want. Reference: "Overriding a tool's standalone env" in notes/tool-environments.md.

Contributed fix — "the packaged setup should change for everyone"

For when you have the repo (editable install) and the fix belongs upstream so every platform benefits.

You will only be testing on the current machine. Assume the existing setup works on other clusters. Make surgical changes to standalone/setup.sh (and other standalone/ files) that fix the current machine while maintaining compatibility with other platforms, using defensive patterns (|| true, conditional checks, graceful fallbacks), then commit them.

Read the full file on GitHub · 170 lines

Files

What ships with it

1 file 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.

PATTERNS.md 18 KB

Changes

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.

1mo ago Changed · +2 lines de1dfcf44682
2mo ago First seen · 168 lines · 202 tokens per session scan C 47c215feec38

Subscribe to this mod's changes

fix-env is a skill published in the GitHub repository evo-design/proto-tools (142 stars, last pushed 2d ago), licensed MIT. It adds 202 tokens to every session and 2,541 once invoked, about $0.0008 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Debugging DevOps and cloud bioengineering bioinformatics generative-biology machine-learning

fix-env next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
fix-envevo-design/proto-tools	Skill	142	2d ago	MIT	C	202	Claude Code
developing-with-streamlitstreamlit/streamlit	Skill	46k	yesterday	Apache-2.0	A	146	Claude Code
rocketride-debugging-pipelinesrocketride-org/rocketride-server	Skill	20k	today	MIT	A	67	Claude Code, Codex
trulens-instrumentationtruera/trulens	Skill	3.6k	today	MIT	A	25	Claude Code, Codex
trulens-diagnosistruera/trulens	Skill	3.6k	today	MIT	A	17	Claude Code, Codex
nonlinear-solversbeita6969/ScienceClaw	Skill	1.0k	yesterday	MIT	A	63	Claude Code
linear-solversbeita6969/ScienceClaw	Skill	1.0k	yesterday	MIT	A	55	Claude Code

proto-tools: Skill for Claude Code