Analysis updated 2026-07-20 · repo last pushed 2026-06-03
Combine a standard proxy subscription with a residential proxy into one clean config.
Generate platform-specific config files for Shadowrocket on iOS, Sparkle on Windows, and FlClash on Android.
Automatically filter out dead or fake proxy nodes so your apps always connect to working servers.
Route specific apps like AI tools or PayPal through a dedicated residential proxy group.
| konbakuyomu/frontier-chain-skeleton | 0xallam/my-recipe | 0xhassaan/nn-from-scratch | |
|---|---|---|---|
| Stars | — | — | 0 |
| Language | Python | Python | Python |
| Last pushed | 2026-06-03 | 2022-11-22 | — |
| Maintenance | Maintained | Dormant | — |
| Setup difficulty | moderate | moderate | moderate |
| Complexity | 3/5 | 2/5 | 4/5 |
| Audience | ops devops | general | developer |
Figures from each repo's GitHub metadata at analysis time.
Requires you to inject private subscription URLs via environment variables at runtime on a server.
frontier-chain-skeleton is a configuration hub for people who manage proxy tools like Shadowrocket (on iOS), Sparkle (on Windows), or FlClash (on Android). Its main job is to merge multiple proxy subscriptions, clean up messy node names, filter out dead or fake nodes, and generate a unified configuration file for each platform. At its core, the project processes subscriptions through a series of scripts. It merges standard proxy subscriptions with "residential" (home broadband) subscriptions, normalizes the node names so they follow a consistent pattern, and removes known bad nodes. The system then generates a final configuration profile that works across Windows and Android, while using a slightly different dual-subscription model for iOS Shadowrocket to handle platform-specific compatibility issues. A person who subscribes to multiple proxy services and wants a clean, unified setup across their phone and computer would use this. For example, if you have a standard airport subscription and a residential proxy, this project combines them and creates a single "residential choice" group. Apps like AI tools or PayPal simply route through that group, meaning you never have to manually pick specific servers or remember which provider a node belongs to. A notable feature of this project is its strict separation of public code and private data. The repository contains no actual subscription links, passwords, or server credentials. All sensitive information is injected temporarily at runtime through environment variables when deploying to a server, and the project includes scripts to safely deploy updates and verify that everything is running correctly without exposing your private URLs. The README also notes that the project has retired older, more complex chaining methods that linked standard proxies to residential ones. It now focuses on a cleaner approach where residential nodes are simply aggregated and filtered dynamically, removing the need for local credential files and making the whole setup easier to maintain.
A tool that merges and cleans up multiple proxy subscriptions, filtering out dead nodes to create one unified config file for apps like Shadowrocket, Sparkle, and FlClash.
Mainly Python. The stack also includes Python.
Maintained — commit in last 6 months (last push 2026-06-03).
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly ops devops.
This repo across BitVibe Labs
Verify against the repo before relying on details.