multi-account-isolation

Multi-Account Isolation Keeping several of your own accounts from being tied together by a platform is not one problem, it is a stack of them. A perfect browser fingerprint fixes exactly one layer. Accounts far more often get linked by an IP, a shared cookie, a mismatched clock, or the same recovery phone number than by a canvas hash. This skill is the checklist. For the code that implements the browser layer, see the anti-detect-browser skill. Scope. This is about accounts you own, or accounts you operate with the holder's authorization - an agency running client profiles, a seller with several storefronts, a team whose ad accounts must not be cross-attributed. It is not about getting into accounts that are not yours, manufacturing fake accounts or engagement, or coming back from a ban you earned; see Acceptable use . Proxy URLs and API keys in the examples always come from the environment. The model: platforms link on many layers, and only need one Linkage systems build a graph. Every account is a node; every shared signal is an edge. One strong edge (same payment card) or several weak ones (same /24 subnet + same screen resolution + same active hours) is enough to merge two nodes into "one operator". So the goal is not "beat the fingerprint test". It is leave no edge . Getting nine layers right and the tenth wrong still merges the nodes. Linkage surface Show more Installs 915 Repository antibrow/anti-d…r-skills GitHub Stars 4 First Seen 2 days ago Security Audits Gen Agent Trust Hub Pass Socket Warn Snyk Fail