labyrinth-dimension

Route blocked network requests through a discovered SOCKS5 proxy and restore state afterward.

Updated Jun 23, 2024
One-click install
npx skills add https://github.com/lifeich1/nixcf --skill labyrinth-dimension-lifeich1
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: labyrinth-dimension
Source: https://github.com/lifeich1/nixcf/tree/main/fool/reasonix/skills/labyrinth-dimension
Command: npx skills add https://github.com/lifeich1/nixcf --skill labyrinth-dimension-lifeich1

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? When direct access to GitHub, package registries, or external APIs fails due to DNS poisoning, connection resets, or geo-blocking, this Skill diagnoses the failure, discovers the correct SOCKS5 proxy endpoint, routes the command through it, and cleans up all proxy state afterward. ## Core Features & Use Cases - Failure classification: Distinguishes proxy-worthy failures (DNS errors, timeouts, resets, HTTP 403/451) from target-side problems (404, 401, 500) before routing anything. - Endpoint discovery: Resolves the SOCKS5 endpoint from existing environment variables, proxychains configuration, or the nixcf flake's typed endpoint data, never guessing an address. - Scoped proxied execution: Runs curl, git, nix, and arbitrary commands through proxychains4 or socks5h:// prefixes, including nix-daemon drop-in management via just proxy and just no-proxy. - Use Case: A nix flake fetch from GitHub times out on a censored network. The Skill confirms the block, finds the proxychains endpoint, prefetches through the proxy, enables the nix-daemon drop-in for the build, then removes it and verifies restoration. ## Quick Start Use the labyrinth-dimension skill to fetch this blocked GitHub repository through the discovered SOCKS5 proxy and restore the network state afterward.

Frequently Asked Questions about labyrinth-dimension

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

FAQPage Schema
How do I route git clone through a SOCKS5 proxy?▼

Use git with an inline proxy configuration: git -c http.proxy=socks5h://HOST:PORT clone <url>. The socks5h scheme resolves DNS at the proxy, which is required when local DNS is poisoned. Discover the endpoint from proxychains.conf or existing environment variables first.

How do I make nix fetch dependencies through a proxy?▼

For client-side fetches, wrap the command with proxychains4 nix flake prefetch or prefix it with https_proxy=socks5h://HOST:PORT. For daemon-side builds, the nix-daemon needs a systemd drop-in, managed in nixcf via just proxy and reverted with just no-proxy.

Why does sudo proxychains4 not proxy my command?▼

sudo sanitizes the environment and strips LD_PRELOAD, which proxychains relies on to intercept libc calls. Use sudo -E proxychains4 to preserve the preload, or configure the target service directly, such as a nix-daemon drop-in, instead of exporting broad variables.

When should I not use a SOCKS5 proxy for a failing request?▼

Do not proxy when the direct route already works, when the target returns HTTP 404, 401, or 500 with a response body, or when the target is a LAN host, localhost, or a configured mirror. Those belong in no_proxy, and a proxy cannot fix target-side errors.

What are the limitations of proxychains with UDP and static binaries?▼

SOCKS5 carries no UDP, so QUIC or HTTP-3-only clients must fall back to TCP. Statically linked binaries and Go programs that bypass libc resolution may ignore the LD_PRELOAD interception entirely; use explicit --socks5-hostname or socks5h:// options for those tools.