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.
npx agentmods add instructions/southliu/south-admin-react/claude-mdgit clone --depth 1 https://github.com/southliu/south-admin-reactWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/southliu/south-admin-react/claude-md)<a href="https://agentmods.dev/instructions/southliu/south-admin-react/claude-md"><img src="https://agentmods.dev/badge/instructions/southliu/south-admin-react/claude-md.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.01717 | $0.01717 |
| Opus 5 | $0.00859 | $0.00859 |
| Sonnet 5 | $0.00343 | $0.00343 |
| Haiku 4.5 | $0.00172 | $0.00172 |
Grade A, and why
south-admin-react 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 212 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.
Commands
Development
pnpm dev # Start dev server (Vite with host flag)
pnpm build # Production build (TypeScript + Vite)
pnpm build:dev # Development build
pnpm build:test # Test environment build
Code Quality
pnpm lint # ESLint with auto-fix
pnpm lint:stylelint # Stylelint for CSS/Less
pnpm prettier # Format code with Prettier
Package Management
pnpm install -w # Install dependencies (use -w for monorepo root)
pnpm i <package> -w # Install new dependencies at workspace root
Git
npx husky install # Reinstall husky hooks if commit fails
Project Architecture
This is a monorepo-based React admin application using pnpm workspaces, built with Vite, TypeScript, React 19, Ant Design, and Zustand.
Monorepo Structure
- Root: Main application in
src/ - packages/: Shared workspace packages
@south/request: HTTP request wrapper@south/message: Global messaging component@south/utils: Shared utilities@south/stylelint: Stylelint configuration
When installing new dependencies, use pnpm i <package> -w to install at the workspace root.
Automatic Route Generation
Routes are automatically generated from the src/pages/ directory structure using vite glob:
// src/router/utils/config.ts
export const ROUTER_EXCLUDE = [
'login', 'forget', 'components', 'utils', 'lib', 'hooks',
'model.tsx', '404.tsx'
];
Route rules:
- File path
src/pages/dashboard/index.tsx→ route/dashboard - File path
src/pages/dashboard/index.tsx→ route/ - Dynamic routes use
[param]syntax:src/pages/user/[id].tsx→ route/user/:id - All
index.tsxfiles have/indexremoved from the route path
Route configuration is in src/router/components/Router.tsx using handleRoutes() helper.
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.
- 5d ago First seen · 212 lines · 1,717 tokens per session scan A 5c9f61a0cfcf
south-admin-react CLAUDE.md is an instructions file published in the GitHub repository southliu/south-admin-react (577 stars, last pushed 2d ago), licensed MIT. It adds 1,717 tokens to every session, about $0.0086 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.
Other instructions, from other repositories
skyroc AGENTS.md
AGENTS.md instructions for Ohh-889/skyroc, covering agents.md, 规范索引, skills 调用规则(关键), 思考顺序 and react 组件规范.
skyroc CLAUDE.md
Claude Code instructions for Ohh-889/skyroc, a project described as: Skyroc 是一个基于 React 19 + TypeScript 的跨端前端工程化 monorepo:既提供开箱即用的 Web 中后台模板(Admin / RuoYi 对接版)和 Expo 移动端业务模板,也把请求、状态、日志、主题、双端 UI 组件库等能力沉淀为边界清晰的 workspace 包。.
ant-design-pro CLAUDE.md
Claude Code instructions for ant-design/ant-design-pro, covering claude.md, project, commands, critical rules and architecture essentials.
v3-admin-vite AGENTS.md
Instructions for un-pany/v3-admin-vite, covering 原则, 1. 编码前思考, 2. 简洁优先, 3. 精准修改 and 4. 目标驱动执行.
pinyin AGENTS.md
Instructions for yunsii/pinyin, covering agents.md, hard rules, 方案与文本靠 side-effect 注册,漏 import 等于没加, vite.config.ts 的 base: '/pinyin/' 不要随手改 and 拼音术语变量名用全拼.
vite-ts-react-template architecture.instructions.md
Instructions for bartstc/vite-ts-react-template, covering architecture rules, project structure, feature slice layers, dependency rule and additional rules.