A README badge is a compact way to disclose that AI tools materially contributed to a project. vibecoded.fyi serves static SVG badges that work in GitHub Markdown without JavaScript or an account.

Open the badge gallery, choose a style, and use the Copy button. The copied Markdown includes the image and a link back to vibecoded.fyi so readers can understand the badge.

[![Proudly Vibe Coded](https://vibecoded.fyi/badges/flat/main/proudly-vibe-coded.svg)](https://vibecoded.fyi/)

Paste it near the top of README.md, usually alongside build, release, or license badges. Commit and push the change, then verify that GitHub renders the image.

Choose the right disclosure

  • Use Proudly Vibe Coded when AI-led conversation or agent work was central to implementation.
  • Add an LLM badge when a model such as Claude, ChatGPT, or Gemini materially powered the project.
  • Add a coding agent badge for tools such as Codex, Claude Code, Cursor, GitHub Copilot, or OpenCode.

You can display more than one, but avoid a wall of badges that hides the project description.

Use HTML when you need sizing control

GitHub allows a limited subset of HTML in Markdown. This example supplies an explicit height while preserving accessible alternative text:

<a href="https://vibecoded.fyi/">
  <img
    src="https://vibecoded.fyi/badges/flat/main/proudly-vibe-coded.svg"
    alt="Proudly Vibe Coded"
    height="20"
  />
</a>

Do not remove the alt text. It gives screen-reader users and readers with blocked images the meaning of the badge.

Add useful context

The badge is more informative when the README includes a short disclosure:

## AI development note

This project was built with [tool names]. AI generated substantial parts of
the implementation; maintainers reviewed the behavior, tests, security-sensitive
paths, and release configuration. See CONTRIBUTING.md for the verification flow.

Adapt the statement honestly. Do not claim review or testing that did not happen.

Badge URLs are stable

Badges are pre-generated SVG files served from predictable paths. Style names include flat, flat-square, for-the-badge, plastic, and terminal. Existing badge URLs remain available when the gallery evolves.

Get into the showcase

The site scans public GitHub usage and lists discovered repositories separately from editorial profiles. A badge does not guarantee coverage. Independent profiles require current badge proof, enough public evidence for a useful story, and factual review under the editorial policy.