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 skills add godmakereth/vibe-coding-tw --skill proxychainsgit clone --depth 1 https://github.com/godmakereth/vibe-coding-twWrote 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.
[](https://agentmods.dev/skills/godmakereth/vibe-coding-tw/proxychains)<a href="https://agentmods.dev/skills/godmakereth/vibe-coding-tw/proxychains"><img src="https://agentmods.dev/badge/skills/godmakereth/vibe-coding-tw/proxychains/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.
<a href="https://agentmods.dev/skills/godmakereth/vibe-coding-tw/proxychains"><img src="https://agentmods.dev/badge/skills/godmakereth/vibe-coding-tw/proxychains.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00049 | $0.02083 |
| Opus 5.5 | $0.00020 | $0.00833 |
| Sonnet 5.5 | $0.00010 | $0.00417 |
| Haiku 4.5 | $0.00005 | $0.00208 |
Grade B, and why
proxychains scanned grade B 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 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sudo apt install proxychains4 # Debian/Ubuntu Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- ❌ curl/wget/git/pip 等命令失敗 This is a copy
97% identical to proxychains — 175 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 292 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Proxychains Network Proxy Skill
自動使用代理解決網路問題 - 當遇到網路連線失敗、超時或訪問受限時,自動使用 proxychains4 強制走代理。
When to Use This Skill
觸發條件(自動應用):
- ❌ Connection timeout errors
- ❌ DNS resolution failures
- ❌ "Connection refused" errors
- ❌ HTTP 403/451 blocked access
- ❌ GitHub/PyPI/npm 等國外資源訪問失敗
- ❌ curl/wget/git/pip 等命令失敗
Claude 應該:
- 檢測到網路錯誤後,自動在命令前新增
proxychains4 - 使用預設代理配置:
http://127.0.0.1:9910 - 如果代理失敗,提示使用者檢查代理服務狀態
Quick Reference
基本用法模式
# ❌ 原命令失敗
curl https://github.com/user/repo
# ✅ 使用代理重試
proxychains4 curl https://github.com/user/repo
常見場景自動應用
場景 1: Git 操作失敗
# 原命令
git clone https://github.com/user/repo.git
# 自動改為
proxychains4 git clone https://github.com/user/repo.git
場景 2: Python pip 安裝失敗
# 原命令
pip install requests
# 自動改為
proxychains4 pip install requests
場景 3: npm/yarn 安裝失敗
# 原命令
npm install package-name
# 自動改為
proxychains4 npm install package-name
場景 4: wget/curl 下載失敗
# 原命令
wget https://example.com/file.tar.gz
# 自動改為
proxychains4 wget https://example.com/file.tar.gz
場景 5: Docker 拉取映象失敗
# 原命令
docker pull image:tag
# 自動改為
proxychains4 docker pull image:tag
場景 6: SSH 連線失敗
# 原命令
ssh user@remote-host
# 自動改為
proxychains4 ssh user@remote-host
配置詳情
預設代理配置
本地代理地址: http://127.0.0.1:9910
配置檔案位置:
~/.proxychains/proxychains.conf(推薦)/etc/proxychains.conf(系統級)
快速配置指令碼
建立使用者級配置(自動使用 127.0.0.1:9910):
mkdir -p ~/.proxychains
cat > ~/.proxychains/proxychains.conf << 'EOF'
# Proxychains configuration
strict_chain
proxy_dns
remote_dns_subnet 224
tcp_read_time_out 15000
tcp_connect_time_out 8000
[ProxyList]
http 127.0.0.1 9910
EOF
環境變數方式(臨時使用)
# 設定代理環境變數
export PROXYCHAINS_SOCKS5_HOST=127.0.0.1
export PROXYCHAINS_SOCKS5_PORT=9910
# 使用
proxychains4 curl https://github.com
工作原理
Proxychains 透過 LD_PRELOAD 機制攔截程式的網路呼叫:
- 攔截系統呼叫:Hook socket 相關的 libc 函式
- 重定向連線:將所有 TCP 連線重定向到代理伺服器
- DNS 代理:透過代理伺服器解析域名
- 透明代理:應用程式無需修改
What ships with it
6 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.
- 1mo ago First seen · 292 lines · 49 tokens per session scan B 2897c724c72c
proxychains is a skill published in the GitHub repository godmakereth/vibe-coding-tw (48 stars, last pushed 10mo ago), licensed MIT. It adds 49 tokens to every session and 2,083 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 2 findings (asks for root, makes network calls). It is 97% identical to proxychains, differing in 175 lines, and is treated as a copy.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
deck-retro
Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…