Borrowing it
Nothing to install: this file belongs to TechHU-GS/cc-discipline. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/TechHU-GS/cc-discipline/main/CLAUDE.mdgit clone --depth 1 https://github.com/TechHU-GS/cc-disciplineWrote 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/techhu-gs/cc-discipline/claude-md)<a href="https://agentmods.dev/instructions/techhu-gs/cc-discipline/claude-md"><img src="https://agentmods.dev/badge/instructions/techhu-gs/cc-discipline/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.1 | $0.03172 | $0.03172 |
| Opus 5 | $0.01586 | $0.01586 |
| Sonnet 5 | $0.00634 | $0.00634 |
| Haiku 4.5 | $0.00317 | $0.00317 |
Grade D, and why
cc-discipline CLAUDE.md scanned grade D with 2 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 yesterday.
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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- **Every `jq` read needs a grep/sed fallback — for EVERY field, not just the obvious one.** git-guard once read `tool_name` with jq alone, so on any jq-less machine it exited 0 at the first check and every destructive-g Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf /tmp/test && mkdir /tmp/test && cd /tmp/test && git init && \ How it starts
The opening of the file, as written. The whole thing — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cc-discipline — CLAUDE.md
General discipline rules are auto-injected via
.claude/rules/. This file is for project-specific information only.
Project Overview
- Project name: cc-discipline
- One-line description: Discipline framework for Claude Code — rules, hooks, skills, and agents that keep AI on track
- Tech stack: Bash (hooks, init.sh, CLI scripts), Node.js (cli.js cross-platform entry), jq (JSON processing)
- Key constraints: Must work on macOS + Linux + Windows (Git Bash). Hook latency baseline is in Known Pitfalls; measure before adding one. Total rules context footprint <3% of 200K context.
Project Structure
├── bin/
│ ├── cli.js ← npm entry point (Node.js, cross-platform)
│ └── cli.sh ← legacy bash CLI
├── lib/
│ ├── status.sh ← `cc-discipline status` command
│ ├── doctor.sh ← `cc-discipline doctor` command
│ └── stack-remove.sh ← `cc-discipline remove-stack` command
├── init.sh ← Main install/upgrade script (interactive + --auto)
├── global/
│ └── CLAUDE.md ← Global rules template (~/.claude/CLAUDE.md)
├── templates/ ← Everything that gets copied to user projects
│ ├── .claude/
│ │ ├── hooks/ ← 7 shell scripts (pre-edit-guard, streak-breaker, etc.)
│ │ ├── rules/ ← 8 core rules (00-07) + stacks/ (5 tech stacks)
│ │ ├── skills/ ← 7 skills (commit, self-check, evaluate, think, summary, investigate, coplan)
│ │ ├── agents/ ← reviewer + investigator subagents
│ │ └── settings.json← Hook registration
│ ├── CLAUDE.md ← Project CLAUDE.md template
│ ├── docs/ ← progress.md + debug-log.md templates
│ └── memory/ ← MEMORY.md template
├── docs/
│ ├── progress.md ← This project's progress log
│ └── debug-log.md ← This project's debug log
└── package.json ← npm package config (version is single source of truth)
Common Commands
# Local test: install to a temp project
rm -rf /tmp/test && mkdir /tmp/test && cd /tmp/test && git init && \
CC_DISCIPLINE_PKG_DIR=~/.cc-discipline \
bash ~/.cc-discipline/init.sh --auto --stack 7
# Test via cli.js
node bin/cli.js --version
node bin/cli.js init --auto --stack 7
# Test a specific hook
echo '{"tool_name":"Bash","tool_input":{"command":"git checkout ."}}' | \
bash templates/.claude/hooks/git-guard.sh 2>&1
# Publish to npm
npm publish
# Upgrade in another project
npx cc-discipline@latest upgrade
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.
- yesterday Changed · +21 lines · -388 tokens per session 2cff7351f9cf
- 2d ago Changed · +7 lines · +367 tokens per session b570d7ab1f43
- 6d ago First seen · 146 lines · 3,193 tokens per session scan D c3be19c3f9de
cc-discipline CLAUDE.md is an instructions file published in the GitHub repository TechHU-GS/cc-discipline (0 stars, last pushed yesterday), licensed MIT. It adds 3,172 tokens to every session, about $0.0159 per session on Opus 5. A static security scan graded it D with 2 findings (reads agent configuration directories, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
plan-forge dapr.instructions.md
Dapr patterns for .NET — building blocks, component config, sidecar architecture, multi-tenant isolation, workflows, state management, secrets.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.