claude-code-hub CLAUDE.md

A repository instruction file for Claude Code, an AI coding assistant, in the ding113/claude-code-hub project. It lists project rules, required checks, development commands, and pull-request requirements.

In plain words
What is it for?
Use it when editing the project, running its build, lint, type checks, and tests, or preparing a pull request for the dev branch.
Why use it?
It tells the coding agent how this project is organized and what must pass before changes are accepted.

Instructions file

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add instructions/ding113/claude-code-hub/claude-md
Clone the repo
git clone --depth 1 https://github.com/ding113/claude-code-hub
Per session 1,512 This file is loaded in full into every session.
When invoked 1,512 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.01512 $0.01512
Opus 5 $0.00756 $0.00756
Sonnet 5 $0.00302 $0.00302
Haiku 4.5 $0.00151 $0.00151

Measured 2d ago against content hash d9746db46874, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

claude-code-hub CLAUDE.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

CLAUDE.md · 144 lines

How it starts

The opening of the file, as written. The whole thing — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

Repository Info

Critical Rules

  1. No Emoji in Code - Never use emoji characters in any code, comments, or string literals
  2. Test Coverage - All new features must have unit test coverage of at least 80%
  3. i18n Required - All user-facing strings must use i18n (5 languages supported). Never hardcode display text
  4. Pre-commit Checklist - Before committing, always run:
    bun run build      # Production build
    bun run lint       # Biome check
    bun run lint:fix   # Biome auto-fix
    bun run typecheck  # TypeScript check (uses tsgo)
    bun run test       # Run Vitest tests
    

Build & Development Commands

# Development
bun install               # Install dependencies
bun run dev               # Run tsgo preflight, then start dev server (port 13500)

# Build & Production
bun run build             # Run tsgo preflight, then build for production
bun run start             # Start production server

# Quality Checks
bun run typecheck         # Type check with tsgo (faster)
bun run lint              # Lint with Biome
bun run lint:fix          # Auto-fix lint issues
bun run format            # Format code

# Testing
bun run test              # Run unit tests (vitest)
bun run test:ui           # Interactive test UI
bun run test:coverage     # Coverage report
bunx vitest run <file>    # Run single test file
bunx vitest run -t "test name"  # Run specific test

# Dev environment (via dev/Makefile)
cd dev && make dev        # Start all services (PG + Redis + app)
cd dev && make db         # Start only database services

Database Migration Workflow

IMPORTANT: Never create SQL migration files manually. Always follow this workflow:

  1. Modify schema - Edit src/drizzle/schema.ts
  2. Generate migration - Run bun run db:generate
  3. Review generated SQL - Check the generated file in drizzle/ directory
  4. Edit if necessary - Make any required adjustments to the generated SQL
  5. Apply migration - Run bun run db:migrate or let AUTO_MIGRATE=true handle it on startup

Read the full file on GitHub · 144 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 144 lines · 1,512 tokens per session scan A d9746db46874

Subscribe to this mod's changes

claude-code-hub CLAUDE.md is an instructions file published in the GitHub repository ding113/claude-code-hub (3,343 stars, last pushed today), licensed MIT. It adds 1,512 tokens to every session, about $0.0076 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.