The software you use, made yours
Describe the change you need, see it work on your own data, and keep your version. No fork, no Git.
Popular right now
Pick one and it becomes your instance, ready to mod.
Your instance first, your change next
One click gives you a link: that link is your account and your running instance. Then you ask for the change in plain words, watch it built against the real code, and keep it only when you have seen it work.
Judge the change before you keep it
Someone asked PostHog for control over their chart colors. The feature existed upstream, locked behind a paid addon. This is what it took to deliver it without crossing that line.
Two copies of the same PostHog
One stays as it is, the other takes the change. Same instance, same insight, same data.
Screenshots from the experiment itself, on a PostHog instance running the mod. The conversation is condensed, the results are not.
Built for real
Every accepted mod becomes a public story: what was asked, what the agent did, and how it was verified. These are the first two, told exactly as they happened.
Open source gave you the right to change it. Now you have the ability.
The license always said yes. Cloning the repository, learning the architecture and keeping a fork alive for years said no, so almost nobody ever did it. The freedom has been real on paper for thirty years. That is the part that changes.
Community is the product, not the funnel
The catalog exists because people publish what they build. The deal is simple and it is the whole business model.
Creation runs on the AI plan you already pay for
Connect Claude, Cursor or ChatGPT and build mods with your own subscription. The free tier is not subsidized generation, it is shared infrastructure.
Public mods, public tests
What you publish ships with its spec and its history, so the next person with your problem installs a proven answer instead of reopening an issue.
Companies pay for privacy, everyone gets the commons
Private mods, audits and guarantees are the paid tier. Public mods ride the release trains while people run them; a mod nobody installs freezes at its last validated version.
Built to leave maintainers better off
A mod layer over other people's projects only survives if those projects gain from it. So that is the design constraint, not a hope.
Revenue share from the first euro
A fixed percentage of what a project's mods earn goes to its maintainers. Policy with a budget, not a promise.
Claimable project pages
Maintainers can claim their project's page, set brand rules and mark mods they endorse or discourage.
Graduation to upstream
Popular mods become clean, attributed pull requests when maintainers want them. Demand data comes with the patch.
An opt-out honored without friction
A project that does not want a mod layer leaves the catalog with one request. The layer only survives if maintainers gain from it existing.