Would you fork someone else's AI economics setup?

That's genuinely the question we've been testing with Leave a Prompt. Not "would you copy a prompt" — you'd fork the actual economics: someone else's provider fallback chain, their spend cap, their approved-model list, all enforced from the moment you fork it. Curious what people here think — would you trust a config enough to fork it into your own account, or does that feel like it needs more proof first?

A few things people usually ask, answering some upfront 👇

What gets copied vs. what stays private?
You're cloning the policy — fallback chain, cap, approved models — not the original owner's API keys, balance, or account access. The fork spins up as a new, independent wallet in your own workspace, enforced against your own keys or balance from the moment it's created.

If the original owner changes their setup later, does my fork update too?
Right now it's a snapshot — you get the config as it exists the moment you fork it, and it's yours to modify from there. Live-sync isn't built yet, but we're weighing it based on how people actually use this.

Is the savings percentage across all forks, or just the best one?
Computed from the usage ledger for that config, aggregated across everyone who's forked and used it — not cherry-picked from the top performer. That's the reason it's tied to the ledger instead of self-reported.

How is this different from just sharing a config file on GitHub?
You could share raw settings as a gist — but you'd lose enforcement (the cap is hard-capped the moment you fork it, not just documented) and verification (the savings number is real usage, not a claim that goes stale the day it's posted).

Genuinely want to hear where this breaks or what's missing — especially on that first question. If forking someone's spend policy still feels like a leap of trust to you, tell us why.