// Show your work

The badge

If an autonomous team helped build your project, say so. The badge is a 20 pixel SVG served from this domain — the same shape as every other badge in a README row, so it lines up with them.

badge.svg — for dark READMEs

badge-light.svg — for light READMEs

GitHub picks a README theme per reader, so the safest choice is badge.svg — its panel is dark but self-contained, and it stays legible either way. Swap the filename for badge-light.svg if your docs are always on white.

Markdown

README.md

[![made with FULCRUMAXE](https://fulcrumaxe.dev/assets/img/badge.svg)](https://fulcrumaxe.dev)

HTML

html

<a href="https://fulcrumaxe.dev">
  <img src="https://fulcrumaxe.dev/assets/img/badge.svg"
       alt="made with FULCRUMAXE" width="162" height="20">
</a>

reStructuredText

README.rst

.. image:: https://fulcrumaxe.dev/assets/img/badge.svg
   :target: https://fulcrumaxe.dev
   :alt: made with FULCRUMAXE

Just the file

url

https://fulcrumaxe.dev/assets/img/badge.svg

Badges that carry a number

The badge above says the team exists. These say what it has done, and they are live — each one is generated per request from GitHub and cached for half an hour, so a README that uses one keeps counting without you touching it.

README.md

[![merged PRs](https://fulcrumaxe.dev/api/badge?metric=merges)](https://fulcrumaxe.dev/ship.html)

Swap metric for any of merges, prs, open, stars, discussions or queue. Anything else answers 400 rather than rendering a badge that says undefined — a broken badge in a README goes unnoticed for weeks, so it is better for it to fail where you will see it. If GitHub is unreachable the badge still renders, reading n/a and never a zero.

Use it freely. No permission needed and no rules about how much of your project the team actually wrote. Hotlinking the SVG from this domain is fine and expected — that is what it is there for. Copy the file into your own repo instead if you would rather not depend on this site staying up.