muhammadhaseebiqbal-dev

Claude Code Leak Source Code — Design skill for Claude Code

Design community

🚨 The leaked source code of Anthropic's Claude Code.

How to install Claude Code Leak Source Code

This entry records only its repository, not the path inside it, so there is no exact command to give. Open muhammadhaseebiqbal-dev/claude-code-leak-source-code and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Claude Code Leak Source Code does

🚨 The leaked source code of Anthropic's Claude Code. Explore 512k+ lines of TypeScript revealing multi-agent swarms, MCP integrations, Bun runtime, and a React/Ink terminal UI.

Alternatives in Design

  • Brand Guidelines — Apply Anthropic's official brand colors and typography to artifacts 94.1k ā˜…
  • Deepclaude — Use Claude Code's autonomous agent loop with DeepSeek V4 Pro, OpenRouter, or any Anthropic-compatible backend 2.3k ā˜…
  • Poco Claw — A more beautiful and easier-to-use alternative to OpenClaw 1.3k ā˜…

README

Claude Code Source Snapshot

**An exploratory mirror of a source snapshot reportedly exposed via published source maps on March 31, 2026**

[![TypeScript](https://img.shields.io/badge/TypeScript-512K%2B_lines-3178C6?logo=typescript&logoColor=white)](#tech-stack) [![Bun](https://img.shields.io/badge/Runtime-Bun-f472b6?logo=bun&logoColor=white)](#tech-stack) [![Files](https://img.shields.io/badge/~1,900_files-source_only-grey)](#directory-structure) [![MCP Server](https://img.shields.io/badge/MCP-Explorer_Server-blueviolet)](#-explore-with-mcp-server)

The raw imported snapshot is preserved in this repository's [`backup` branch](https://github.com/muhammadhaseebiqbal-dev/claude-code-leak-source-code/tree/backup). The `main` branch contains added documentation, tooling, and repository metadata.


Table of Contents


The Story: How the Source Code Leaked

On March 31, 2026, the developer community was stunned when the entire uncompiled TypeScript source code for Anthropic's flagship CLI tool, Claude Code, was exposed to the public. The leak wasn't the result of a sophisticated hack or an insider threat, but a simple build configuration oversight