ingenious: Command for Claude Code

.claude/commands/ai-config/prune-claude-md.md

prune-claude-md is a command for Claude Code from Insight-Services-APAC/ingenious. It costs 0 tokens per session (525 once invoked), scanned A, original, MIT.

A command that shortens a CLAUDE.md file, which contains instructions for a coding agent, to its most important project-specific guidance.

In plain words
What is it for?
Use it to remove general advice and duplication while keeping commands, constraints, project-specific patterns, and known pitfalls.
Why use it?
Long or repeated instructions can distract an agent and make key rules harder to follow. The command focuses the file on build, test, architecture, and safety details.

Command for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions CLAUDE.md.

This is Insight-Services-APAC/ingenious's own configuration. It tells Claude Code how to work on ingenious itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything ingenious configures →

Reuse

Borrowing it

Nothing to install: this file belongs to Insight-Services-APAC/ingenious. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/Insight-Services-APAC/ingenious/main/.claude/commands/ai-config/prune-claude-md.md
Clone the repo
git clone --depth 1 https://github.com/Insight-Services-APAC/ingenious

Made for: Claude Code.

Wrote 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.

agentmods badge for prune-claude-md

README.md
[![agentmods](https://agentmods.dev/badge/commands/insight-services-apac/ingenious/prune-claude-md/github.svg)](https://agentmods.dev/commands/insight-services-apac/ingenious/prune-claude-md)
Your own site
<a href="https://agentmods.dev/commands/insight-services-apac/ingenious/prune-claude-md"><img src="https://agentmods.dev/badge/commands/insight-services-apac/ingenious/prune-claude-md/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for prune-claude-md

Your own site · 80×15
<a href="https://agentmods.dev/commands/insight-services-apac/ingenious/prune-claude-md"><img src="https://agentmods.dev/badge/commands/insight-services-apac/ingenious/prune-claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 525 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00000 $0.00525
Opus 5 $0.00000 $0.00262
Sonnet 5 $0.00000 $0.00105
Haiku 4.5 $0.00000 $0.00052

Measured 4d ago against content hash ed7ec4dfdf19, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

prune-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 4d 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/commands/ai-config/prune-claude-md.md · 78 lines

How it starts

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

Prune CLAUDE.md

Reduce CLAUDE.md to only the most essential information for effective agent performance. Target: 300 lines maximum.

Principles for Pruning

Keep information that:

  • Directly affects code generation (coding standards, patterns to follow)
  • Prevents common mistakes (critical gotchas, forbidden patterns)
  • Enables task completion (how to build, test, run)
  • Is unique to this project (not general knowledge)

Remove information that:

  • Claude already knows (general best practices, language syntax)
  • Is redundant or repeated
  • Is too verbose when a shorter version suffices
  • Describes obvious project structure
  • Contains examples that can be inferred from code

Step 1: Analyze Current Size

wc -l CLAUDE.md

Step 2: Categorize Content by Priority

Priority 1 - Must Keep:

  • Project-specific commands (build, test, run)
  • Critical constraints or requirements
  • Non-obvious architectural decisions
  • Environment setup essentials

Priority 2 - Keep if Space Allows:

  • Code style preferences beyond linting
  • Common gotchas specific to this codebase
  • Key file locations for important modules

Priority 3 - Remove:

  • General programming advice
  • Lengthy explanations of standard tools
  • Verbose examples when terse ones work
  • Aspirational guidelines not enforced

Step 3: Apply Compression Techniques

  1. Consolidate related points into single concise statements
  2. Use bullet points instead of paragraphs
  3. Remove filler words and unnecessary qualifiers
  4. Replace examples with patterns where possible
  5. Link to docs instead of duplicating documentation
  6. Use code blocks sparingly - only for non-obvious commands

Step 4: Restructure for Scanning

Organize remaining content:

# CLAUDE.md
## Quick Reference (commands, key paths)
## Constraints (must-follow rules)
## Patterns (how things are done here)
## Gotchas (common mistakes to avoid)

Step 5: Validate Final Size

wc -l CLAUDE.md

Read the full file on GitHub · 78 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. 4d ago First seen · 78 lines · 0 tokens per session scan A ed7ec4dfdf19

Subscribe to this mod's changes

prune-claude-md is a command published in the GitHub repository Insight-Services-APAC/ingenious (24 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 525 tokens. 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-09-04.