BuiltByBadge

Your sites don’t know about each other.

BuiltByBadge is a skill for Claude, ChatGPT, and coding agents. One conversation sets up your badge and your hub page. Then every time you ship a site, your assistant asks one question: want your badge on this? Three lines of static HTML. Nothing hosted, nothing to break.

Free covers the Face and Ink badges and your hub. Pro is one payment, not a subscription.

Works with ClaudeClaude CodeChatGPTCursorany agent with skills

Badge style
yoursite.dev
Your assistant pastes this before </body>
<!-- BuiltByBadge -->
<a href="https://yoursite.dev/built" target="_blank" rel="me noopener" style="position:fixed;right:16px;bottom:16px;display:inline-flex;align-items:center;gap:8px;font:500 13px/1 system-ui;color:#1a1815;background:#fff;border:1px solid #d9d3c5;padding:6px 14px 6px 6px;border-radius:99px;text-decoration:none;box-shadow:0 2px 10px rgba(26,24,21,.08)">
<img src="https://yoursite.dev/built/avatar.jpg" width="22" height="22" style="border-radius:50%"> Built by @maria</a>

The problem isn’t shipping. It’s what happens after.

You post the launch. It spikes. Two days later the chart is flat and the site might as well be invisible. That’s not failure; it’s just how launches work. They’re events, and events end.

Meanwhile you’ve already built five, eight, twelve other things. Each one gets its own trickle: a little search traffic, an old backlink, someone’s bookmark. Six trickles, six dead ends. Nobody who lands on one of them has any way to find the rest, so the audience you earned on every previous launch does nothing for the next one.

Connect them and the math changes. Every visitor to any of your sites becomes one click from all of them, and each launch starts with everyone who ever found your work instead of starting from zero. That’s all BuiltByBadge is: the plumbing that makes your work compound. It just happens to install itself.

How it works

1

Install the skill

Drop one file into Claude, ChatGPT, Cursor, or whatever you build with. That’s the whole product. There is no account.

2

One conversation

Your assistant interviews you, shows you your badge and hub live, and lets you change anything. No website yet? It sets up free hosting in your name.

3

It remembers for you

Every time you finish a site in chat, it asks once. Say yes and the badge is in, and the project is on your hub.

You never hand-edit a link again. Ship something new, say yes once, and every badge you’ve ever placed already points to the right place.

One badge, five styles

Every style is the same three lines with different inline styles. Pick one in the setup conversation, or bring your brand colors and the skill builds yours, contrast-checked.

Three lines that outlive everything

Most badge widgets are drawn by JavaScript, which means three quiet problems: crawlers mostly don’t run scripts, so search engines never see the link; the script can block or break your page; and when the service behind it shuts down, every badge dies at once. Some widget services even tell you to keep a separate plain HTML link next to the widget for SEO. That plain link is the part doing the work.

So we skipped the widget. Your badge is an anchor tag in the HTML itself. Every site you ship carries a real, crawlable backlink to your hub, it renders before your stylesheet finishes loading, and there is no server anywhere whose bad day becomes yours.

≈200bytes of HTML
0network requests, text styles
0lines of JavaScript
1URL, forever

Where the badge leads

One page, wherever you want it: a path on your own domain, your company site, or free hosting the skill sets up in your name in a few minutes. Your face, one line about you, your top three projects, and everything else one tap deeper.

When you ship something new, this page gets one more row. That is the entire maintenance burden of the system, and your assistant does it for you. Every badge you have ever placed points here, so they are all current the moment this page is.

It comes in a light theme, a dark theme, or your brand, and every link on it opens in a new tab. Tap the badge in the corner of this page to see ours.

Pricing

Free to start. One payment if you want it in your colors.

Free

$0

  • The full setup conversation and hub page
  • Face and Ink badge styles
  • Small BuiltByBadge line on your hub
Download the skill

Pro one time

$29

  • All five badge styles, including Glass
  • Your brand colors, pulled from your site or logo
  • No BuiltByBadge branding anywhere
  • Lifetime updates, unlimited sites
Get Pro

One payment. Not a subscription.

Questions

What exactly am I buying?

A skill file and the system inside it: the setup conversation, five badge styles, the hub page template, and the ship-time prompt that adds your badge to new sites. It runs inside the AI you already use. There is no service behind it.

Do you host my hub?

No. Your hub is one HTML file on a site you control. If you don’t have one, the skill sets up free hosting like GitHub Pages, in your name, in a few minutes. Nothing of ours can go down and take your badges with it.

Why static HTML instead of a script?

A script can break, block rendering, or vanish with the service that serves it, and crawlers can’t see what a script draws. The badge is a real link on every page: it loads instantly, works everywhere, and every site you ship becomes a real backlink to your hub.

I shipped something new. Do I update every badge?

No. Your assistant adds one row to your hub. Every badge already out there points at the hub, so they’re all current the moment the hub is.

Which assistants does it work with?

Claude and Claude Code natively. ChatGPT via a project or custom GPT. Cursor and similar coding agents via their rules file. A porting guide for all of them ships inside the skill.

How do I install it?

One step per platform. Claude: save the .skill file. ChatGPT: paste the instructions into a project or custom GPT and upload three knowledge files. Cursor: drop a rules file into your project. Codex, Copilot, and the rest: add one section to AGENTS.md. Each version ships with its own one-page install guide, and then you just say “set up my builtbybadge.”

Can I use it in more than one assistant?

Yes. Pro includes every platform version, and they all read the same profile file, so your badge and hub stay identical whether today’s site gets built in Claude Code or Cursor.

What if it’s not for me?

Email hi@builtbybadge.com within 30 days and you get your money back. No form, no questions asked.

What stops me from using Pro features without paying?

Honestly, nothing but the honor system. It’s $29 once for something you’ll put on every site you ever ship. If it’s useful and you can afford it, pay for it. If you can’t yet, ship things and come back.

BuiltByBadge is part of the SideRoad portfolio, building toward $1M in public, and this site was designed and shipped with ShipWolf. The badge in the corner of this page is the product itself, running its own production markup. Tap it.

Built by @gloverbuilds