proxychains

Name: proxychains
Availability: InStock
Author: anliang0306

Detect network failures and rerun commands through proxychains4 via a local proxy.

1|Updated Dec 20, 2025

Search Tags:#automation #DNS #proxychains #CLI-tools #command-wrapping #network-proxy #HTTP-proxy

Ready to run

npx skills add https://github.com/anliang0306/VIBE-CODING-CN --skill proxychains-anliang0306

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: proxychains
Source: https://github.com/anliang0306/VIBE-CODING-CN/tree/main/i18n/zh/skills/proxychains
Command: npx skills add https://github.com/anliang0306/VIBE-CODING-CN --skill proxychains-anliang0306

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill automatically detects network issues and applies proxychains4 to commands, enabling seamless work when connections are unstable or blocked by routing traffic through a local proxy.

Core Features & Use Cases

Automatic command wrapping: When a command fails due to timeouts, DNS failures, or access blocks, the skill automatically prefixes it with proxychains4.
Unified proxy configuration: Uses a local proxy at http://127.0.0.1:9910 and a standard proxychains.conf to route traffic.
Use Case: In CI/CD pipelines or development workflows, ephemeral blocks on GitHub, PyPI, or Docker pulls are automatically bypassed via the proxy chain.

Quick Start

Ensure a proxy is running on 127.0.0.1:9910 and that ~/.proxychains/proxychains.conf exists with a ProxyList including http 127.0.0.1 9910.
Run your command with proxychains4, e.g. proxychains4 curl https://github.com.
If the proxy fails, verify the proxy service status and the proxychains configuration.

Frequently Asked Questions about proxychains

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automatically route curl or git traffic through a local HTTP proxy?▼

To automatically route traffic through a local HTTP proxy, this skill detects network failures like timeouts or DNS blocks and prefixes commands such as curl or git with proxychains4. It wraps the command to bypass access blocks using a local proxy.

What causes Docker pull or GitHub access block failures and how can I bypass them?▼

Access block failures for Docker pulls or GitHub are often caused by DNS failures or network timeouts. You can bypass these ephemeral blocks by routing the command through a local proxy using proxychains4.

Do I need a specific proxy configuration to use proxychains for network issues?▼

Yes, to use proxychains for network issues, you need a local proxy running at 127.0.0.1:9910 and a valid proxychains.conf file. The configuration file must include a ProxyList entry pointing to the local HTTP proxy.

How does command wrapping with proxychains4 work for CLI tools?▼

Command wrapping with proxychains4 for CLI tools works by automatically detecting when a command fails due to network restrictions. It then re-executes the command with proxychains4 prefixed, forcing the traffic through the configured local proxy.

Why does proxychains fail to route traffic even when the local proxy is running?▼

Proxychains fails to route traffic when the proxychains.conf is missing or misconfigured. Verify that the configuration file exists at the expected path and correctly lists the local proxy at 127.0.0.1 port 9910.

Can I use this network proxy automation in CI/CD pipelines?▼

Yes, you can use this network proxy automation in CI/CD pipelines. It seamlessly handles unstable connections by automatically wrapping failed commands with proxychains4, ensuring continuous integration workflows bypass access blocks.