How to Add the Anti-996 Badge to Your GitHub Project

TLDR: Add the Anti-996 badge to your GitHub project by copying the Markdown snippet from the externals/instruction.md file in the 996icu/996.ICU repository and pasting it into your README.md.

The 996.ICU repository provides ready-to-use badge snippets that allow developers to visually protest against the "996" work schedule. Adding the Anti-996 badge to your GitHub project requires only embedding a Shields.io image link that connects to the 996.icu website.

Locating the Official Badge Markup

The official documentation for the Anti-996 badge resides in externals/instruction.md within the 996icu/996.ICU repository. According to the source code analysis, the standard badge markup appears at lines 5-13, while the license badge markup is located at lines 18-22. This file provides both HTML and Markdown versions, though Markdown is the standard format for GitHub README files.

Steps to Add the Anti-996 Badge to Your GitHub Project

Standard Anti-996 Badge

To display the primary Anti-996 badge, insert the following Markdown snippet into your README.md file:

[![996.icu](https://img.shields.io/badge/link-996.icu-red.svg)](https://996.icu)

Place this snippet wherever you want the badge to appear—typically at the top of your README alongside other status badges. This code renders a red Shields.io badge linking directly to the 996.icu website.

Anti-996 License Badge (Optional)

If your project adopts the Anti-996 License, you can add an additional badge referencing the license file:

[![LICENSE](https://img.shields.io/badge/license-Anti%20996-blue.svg)](https://github.com/996icu/996.ICU/blob/master/LICENSE)

This badge visually communicates that your repository uses the Anti-996 License as defined in the repository's LICENSE file.

Verification and Rendering

Once you have inserted the appropriate Markdown snippet from externals/instruction.md into your project's README.md, commit the changes and push them to GitHub. The badge renders automatically via Shields.io services. You can verify the implementation by examining the live example in the 996.ICU repository's own README.md (lines 9-13), which demonstrates the badge in production.

Summary

• The 996icu/996.ICU repository maintains official badge markup in externals/instruction.md
• Two badge variants exist: a standard red link badge (externals/instruction.md#L5-L13) and an optional blue license badge (externals/instruction.md#L18-L22)
• Implementation requires only copying Markdown snippets into your README.md
• Badges render automatically via Shields.io without additional dependencies
• The repository's own README.md#L9-L13 serves as a live implementation reference

Frequently Asked Questions

Where is the official badge markup documented?

The official badge markup is documented in the externals/instruction.md file within the 996icu/996.ICU repository. This file contains both HTML and Markdown code snippets at specific line ranges (lines 5-13 for the standard badge, lines 18-22 for the license badge) for easy integration into any project.

What is the difference between the standard badge and the license badge?

The standard badge is a red Shields.io image linking to https://996.icu, serving as a general statement against 996 work schedules. The license badge is a blue Shields.io image specifically indicating that the project uses the Anti-996 License, linking directly to the license file at github.com/996icu/996.ICU/blob/master/LICENSE.

Can I use the Anti-996 badge in private repositories?

Yes, you can add the badge to private repositories by including the Markdown snippet in your README.md. However, the badge will only be visible to users who have access to view the private repository, unlike public repositories where the badge contributes to the public 996.ICU movement.

Does adding the badge require including the Anti-996 License in my project?

No, adding the standard Anti-996 badge does not require adopting the Anti-996 License. The badge functions as an independent statement. However, if you choose to display the license badge, you should ensure your project actually uses the Anti-996 License as referenced in the badge's link to the 996.ICU repository.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}