docs: refresh README/docs/examples + install scripts for waves 1-4

User-facing documentation drifted behind several waves of feature work
(plugin manifest, hooks, sync command, --weekly, audit skills, Karpathy
skill, CLAUDE.local.md tier, layered hook config). Refresh + fix one
real install bug. Surgical edits only — no rewrites.

README.md:
  - "What's New" block now reflects the plugin manifest, --weekly,
    InstructionsLoaded hook, AGENTS.md interop, CLAUDE.local.md tier,
    layered hook config, and the fail-closed guardian.
  - "What's Included" expanded from 5 numbered bullets to a structured
    list grouping the 5 skills (incl. three forked audit skills),
    2 slash commands, 1 agent, and 3 hook scripts.
  - Components Deep Dive: /sync-claude-md and the guardian's fail-closed
    contract now documented.
  - Project Status: 1.0.0 -> 2.1.0; Quick Stats updated to reflect
    actual component counts.
  - Acknowledgments: attribution to MIT-licensed forrestchang and
    shanraisshan source repos for adapted patterns.

docs/ARCHITECTURE.md, docs/QUICK_START.md, docs/TROUBLESHOOTING.md,
docs/INSTALLATION.md, examples/modular-setup.md, examples/integration-
examples.md:
  - Every "20-300 lines" / ">300 lines" / "exceeds 300 lines" reference
    rewritten to the actual 150-line hard cap.
  - Every ls/Remove-Item path that pointed at the legacy
    ~/.claude/commands/enhance-claude-md/ bundle now points at the
    top-level enhance-claude-md.md + sync-claude-md.md files.
  - integration-examples.md line-bounds shell guard now uses 20..150.

docs/CLAUDE.md:
  - Install-verify ls list extended with the three new audit-skill
    directories so docs match what install.sh actually creates.

install.sh + install.ps1 (REAL FIX, not just docs):
  - The three forked audit skills (claude-md-drift-audit, link-check,
    dependency-rescan) were registered in plugin.json but never copied
    by the direct-install path. Both installers now iterate over them
    after the karpathy-guidelines block, mirroring the same backup +
    nested-duplicate-cleanup pattern. Banner section and uninstall
    instructions list all 5 skills.

Verified:
  - All 5 CLAUDE.md files in this repo still <= 150 lines after edits.
  - install.sh passes bash -n syntax check.
  - Plugin manifest still resolves all 8 referenced paths on disk.
  - README invariants present: 2.1.0, --weekly, hooks/hooks.json,
    both source-repo attributions, three audit skill names.
  - Stale-claim sweep: zero "20-300" / ">300" / "exceeds 300" refs
    remain in docs/ or examples/.

README.md

@@ -12,16 +12,20 @@ ClaudeForge is a comprehensive toolkit that eliminates the tedious process of ma
 
 ---
 
-## 🆕 New in v2.0 (Claude Code v2.1.4+ Support)
+## 🆕 What's New
 
-- **Lifecycle Hooks**: Guardian agent automatically checks for updates at session start using SessionStart hooks
-- **Modern Permissions**: All components now use `permissions:` syntax for fine-grained control
-- **Hot-Reload**: Skills automatically reload when modified (no restart needed)
-- **Fork-Safe Mode**: Guardian runs independently with `fork_safe: true` without blocking operations
-- **Version Detection**: Installers validate Claude Code version and ensure compatibility
-- **Auto-Migration**: Seamless upgrade from v1.x with automatic backups
+- **Installable Claude Code plugin** — manifest at `.claude-plugin/plugin.json`; install with `/plugin marketplace add alirezarezvani/ClaudeForge && /plugin install claudeforge`
+- **Hard 150-line cap per CLAUDE.md** — enforced deterministically by `hooks/hooks.json` on `PostToolUse(Edit|Write)` *and* `InstructionsLoaded` (every `load_reason`); larger projects spread content across chained sub-files via `@path` imports
+- **`/sync-claude-md`** — walks every CLAUDE.md, prunes stale references, splits when over the cap, repairs root ↔ sub chains
+- **`/sync-claude-md --weekly`** — orchestrates three forked task-style skills in parallel: `claude-md-drift-audit`, `claude-md-link-check`, `claude-md-dependency-rescan`
+- **Karpathy behavioural guidelines** auto-embedded in every generated CLAUDE.md and installed as a standalone `~/.claude/skills/karpathy-guidelines/` skill scoped to code-file globs
+- **`AGENTS.md` / `.cursorrules` / `.windsurfrules` interop** — `/enhance-claude-md` detects sibling instruction files and chains them via `@`-imports instead of overwriting
+- **`CLAUDE.local.md` personal tier** — per-developer overrides exempt from the cap, gitignored automatically
+- **Layered hook config** — `hooks/hooks-config.json` (committed defaults) + `hooks/hooks-config.local.json` (gitignored) lets developers opt out per machine
+- **Lifecycle hooks**: `SessionStart`, `PreToolUse`, `PostToolUse`, `InstructionsLoaded`, `Stop` (one-line drift summary at session end)
+- **Guardian agent** runs `model: haiku` with a fail-closed contract (Skill-tool only, never auto-commits, aborts on missing validated output)
 
-👉 **Upgrading from v1.x?** See [docs/MIGRATION_V2.md](docs/MIGRATION_V2.md) for migration guide.
+👉 **Upgrading from v1.x?** See [docs/MIGRATION_V2.md](docs/MIGRATION_V2.md).
 
 ---
 
@@ -40,20 +44,29 @@ ClaudeForge is a comprehensive toolkit that eliminates the tedious process of ma
 
 ## 📦 What's Included
 
-### 1. **Skill** (`claudeforge-skill`)
-Core capability for CLAUDE.md analysis, generation, validation, and enhancement
+### Skills
 
-### 2. **Slash Command** (`/enhance-claude-md`)
-Interactive interface with multi-phase discovery workflow. Delegates deep codebase scans to the Explore subagent so the discovery does not bloat the calling session.
+1. **`claudeforge-skill`** (`skill/SKILL.md`) — core analysis / validation / generation engine; runs on `model: haiku`. Scoped via `paths:` to `CLAUDE.md`, `CLAUDE.local.md`, `AGENTS.md`, `.cursorrules`, `.windsurfrules`, and `.claude/rules/*.md` so it auto-loads only when those files are touched.
+2. **`karpathy-guidelines`** (`skill/karpathy-guidelines/SKILL.md`) — Think Before Coding, Simplicity First, Surgical Changes, Goal-Driven Execution. Embedded into every generated CLAUDE.md and installed as a standalone skill `paths:`-scoped to ~23 source-file extensions. Adapted with attribution from the MIT-licensed [forrestchang/andrej-karpathy-skills](https://github.com/forrestchang/andrej-karpathy-skills).
+3. **`claude-md-drift-audit`** (`skill/claude-md-drift-audit/SKILL.md`, forked + `agent: Explore`) — walks the last N days of git history and flags every CLAUDE.md line that references deleted paths, renamed paths, or removed dependencies. Read-only. `/claude-md-drift-audit [days=7]`.
+4. **`claude-md-link-check`** (`skill/claude-md-link-check/SKILL.md`, forked + `agent: Explore`) — verifies every `@path` chain import and every relative markdown link inside every CLAUDE.md resolves. Read-only. `/claude-md-link-check [path-glob]`.
+5. **`claude-md-dependency-rescan`** (`skill/claude-md-dependency-rescan/SKILL.md`, forked + `agent: Explore`) — diffs declared dependencies (`package.json` / `requirements.txt` / `pyproject.toml` / `go.mod` / `Cargo.toml`) against the Tech Stack section of every CLAUDE.md. Read-only. `/claude-md-dependency-rescan [manifest]`.
 
-### 3. **Slash Command** (`/sync-claude-md`)
-Walks every CLAUDE.md in the project, prunes stale references (removed dependencies, deleted files, dead modular links), enforces the **150-line hard cap per file**, and repairs the root ↔ subdirectory chain (markdown links + `@path` imports). Run after refactors, dependency changes, or before cutting a release.
+### Slash commands
 
-### 4. **Guardian Agent** (`claude-md-guardian`)
-Background agent for automatic CLAUDE.md maintenance and synchronization
+- **`/enhance-claude-md`** (`command/enhance-claude-md.md`) — multi-phase init/enhance workflow with `argument-hint`, `when_to_use`, `allowed-tools`, and `disallowedTools` (blocks `WebFetch` / `WebSearch`). Delegates deep codebase scans to the Explore subagent.
+- **`/sync-claude-md`** (`command/sync-claude-md.md`) — inventory → prune stale refs → enforce the 150-line cap → repair root ↔ sub chain. **New `--weekly` flag** orchestrates the three audit skills in parallel before doing sync work.
 
-### 5. **Karpathy Guidelines Skill** (`karpathy-guidelines`)
-Behavioral guardrails — Think Before Coding, Simplicity First, Surgical Changes, Goal-Driven Execution — installed as a standalone skill and automatically embedded into every CLAUDE.md generated or enhanced by `/enhance-claude-md`. Adapted with attribution from the MIT-licensed [forrestchang/andrej-karpathy-skills](https://github.com/forrestchang/andrej-karpathy-skills) repository, inspired by Andrej Karpathy's observations on common LLM coding failure modes.
+### Agent
+
+- **`claude-md-guardian`** (`agent/claude-md-guardian.md`) — background maintenance. Runs `model: haiku` with a fail-closed contract: Skill-tool only, aborts on missing validated output, never auto-commits, respects the local hook config.
+
+### Hooks
+
+- **`hooks/hooks.json`** — wires `PostToolUse(Write|Edit)`, `InstructionsLoaded` (all five `load_reason` values), and `Stop` events to scripts under `hooks/`.
+- **`hooks/validate-claude-md.py`** — enforces the 150-line cap deterministically at load time *and* write time; exempts `*.local.md`; exits with stderr feedback on violation.
+- **`hooks/audit-claude-md.py`** — `Stop` hook; one-line CLAUDE.md health summary printed at session end (total tracked / over cap / near cap).
+- **`hooks/hooks-config.json`** + **`hooks/hooks-config.local.json`** — layered config; per-developer overrides without forking the shipped manifest.
 
 ---
 
@@ -217,18 +230,15 @@ See the [examples/](examples/) directory for:
 
 ### **Slash Command: /enhance-claude-md**
 
-**Multi-Phase Workflow:**
-1. **Discovery** - Checks for existing CLAUDE.md, examines project structure
-2. **Analysis** - Determines appropriate action (initialize vs. enhance)
-3. **Task** - Invokes skill or agent to execute workflow
+**Multi-phase workflow** (Discovery → Analysis → Task). Discovery delegates the deep codebase walk to the Explore subagent so it doesn't bloat the calling session. Phase 1 also detects sibling `AGENTS.md` / `.cursorrules` / `.windsurfrules` and chains them via `@`-imports rather than overwriting. Phase 3 invokes `claudeforge-skill` via the Skill tool.
+
+### **Slash Command: /sync-claude-md (with `--weekly`)**
+
+Default mode: inventory every CLAUDE.md, prune stale references, enforce the 150-line cap by splitting into sub-files, repair the root ↔ sub chain. With `--weekly`, **Phase 0** issues the three forked audit skills (`claude-md-drift-audit`, `claude-md-link-check`, `claude-md-dependency-rescan`) in parallel via the Skill tool, aggregates their findings under `## Weekly Audit Summary`, then proceeds. Each forked skill runs in an isolated subagent context (`context: fork`, `agent: Explore`) so audit work doesn't bloat the calling session.
 
 ### **Agent: claude-md-guardian**
 
-**Background Maintenance:**
-- **Auto-Sync** - Updates CLAUDE.md based on detected changes
-- **Smart Detection** - Only updates when significant changes occur
-- **Token-Efficient** - Uses haiku model for routine updates
-- **Milestone-Aware** - Triggers after feature completion, refactoring, etc.
+Runs `model: haiku`, `fork_safe: true`. Hook frontmatter uses Anthropic's canonical keyed-object schema (events: `SessionStart`, `PreToolUse`, `PostToolUse`, `InstructionsLoaded`). **Fail-closed contract**: invokes `claudeforge-skill` exclusively through the Skill tool (never inlines SKILL.md), aborts on missing validated output, never auto-commits, respects `hooks/hooks-config.local.json`.
 
 ---
 
@@ -271,27 +281,30 @@ This project is licensed under the MIT License - see the [LICENSE](LICENSE) file
 
 ## 🙏 Acknowledgments
 
-- Built for the [Claude Code](https://claude.com/claude-code) community
-- Inspired by best practices from Anthropic's official documentation
-- Special thanks to all contributors and early adopters
+- Built for the [Claude Code](https://claude.com/claude-code) community.
+- The behavioural-guardrail skill adapts the four principles from the MIT-licensed [forrestchang/andrej-karpathy-skills](https://github.com/forrestchang/andrej-karpathy-skills) (inspired by Andrej Karpathy's commentary on LLM coding pitfalls). Original prose; attribution preserved in `skill/karpathy-guidelines/SKILL.md`.
+- Several plugin conventions (layered hook config, `Stop` audit hook, command discovery metadata, `paths:` scoping on skills, fail-closed contracts) are adapted from the MIT-licensed [shanraisshan/claude-code-best-practice](https://github.com/shanraisshan/claude-code-best-practice). Patterns implemented in original code with attribution in `CHANGELOG.md`.
+- Anthropic's [Claude Code documentation](https://code.claude.com/docs/en/memory) drove the load-event integrations (`InstructionsLoaded`, all five `load_reason` matchers) and the `context: fork` task-style skills.
 
 ---
 
 ## 🚦 Project Status
 
-**Version:** 1.0.0
+**Version:** 2.1.0 (see [CHANGELOG.md](CHANGELOG.md))
 **Status:** ✅ Stable & Production-Ready
-**Last Updated:** November 12, 2025
+**Requires:** Claude Code 2.1.4+ for hooks/`InstructionsLoaded`/`paths:` features
 
 ---
 
 ## 📊 Quick Stats
 
-- **7** reference CLAUDE.md templates included
-- **100%** native Claude Code format compliance
-- **5** Python modules
-- **3** integrated components (skill, command, agent)
-- **10+** usage examples and scenarios
+- **5** skills (`claudeforge-skill`, `karpathy-guidelines`, plus three forked audit skills)
+- **2** slash commands (`/enhance-claude-md`, `/sync-claude-md` with `--weekly`)
+- **1** agent (`claude-md-guardian`, fail-closed contract)
+- **3** hook scripts wired across `PostToolUse`, `InstructionsLoaded`, `Stop`
+- **5** Python modules under `skill/` (analyzer, validator, generator, template_selector, workflow)
+- **7** reference CLAUDE.md templates under `skill/examples/`
+- **150** — hard line cap per CLAUDE.md, enforced at load time *and* write time
 
 ---
 

docs/ARCHITECTURE.md

@@ -211,9 +211,10 @@ def calculate_quality_score(self) → int:
 **Validation Categories:**
 
 1. **Length Validation**
-   - Recommended: 20-300 lines
-   - Warning: 300-400 lines (suggest modular)
-   - Error: < 20 or > 400 lines
+   - Recommended: 20–120 lines (sweet spot)
+   - Warning: 120–150 lines (approaching cap)
+   - **Hard cap: 150 lines** — enforced deterministically by `hooks/validate-claude-md.py` on `PostToolUse(Edit|Write)` *and* `InstructionsLoaded`. Files over the cap must be split into chained sub-CLAUDE.md files.
+   - Exempt: any file whose basename ends in `.local.md` (personal-tier override).
 
 2. **Structure Validation**
    - Required sections: Core Principles, Tech Stack, Workflow
@@ -432,9 +433,9 @@ Triggers update if:
 
 ### File Size Limits
 
-- Single file: Max 400 lines (prefer 300)
-- Modular files: Each 150-300 lines
-- Total project: Unlimited with modular
+- Every CLAUDE.md: hard cap 150 lines (no exceptions outside `*.local.md`).
+- Modular split via `@path/to/sub/CLAUDE.md` chain imports when content would exceed the cap.
+- Total project: unlimited via modular chaining + `.claude/rules/*.md` for path-scoped guidance.
 
 ### Caching Strategy
 

docs/CLAUDE.md

@@ -19,6 +19,9 @@ Operational guidance for installers, smoke tests, and release management.
 # Verify after install:
 ls -la ~/.claude/skills/claudeforge-skill/
 ls -la ~/.claude/skills/karpathy-guidelines/
+ls -la ~/.claude/skills/claude-md-drift-audit/
+ls -la ~/.claude/skills/claude-md-link-check/
+ls -la ~/.claude/skills/claude-md-dependency-rescan/
 ls -la ~/.claude/commands/enhance-claude-md.md
 ls -la ~/.claude/commands/sync-claude-md.md
 ls -la ~/.claude/agents/claude-md-guardian.md

docs/INSTALLATION.md

@@ -173,7 +173,7 @@ examples/
 
 ```bash
 # macOS/Linux
-ls -la ~/.claude/commands/enhance-claude-md/
+ls -la ~/.claude/commands/enhance-claude-md.md ~/.claude/commands/sync-claude-md.md
 
 # Windows
 dir $env:USERPROFILE\.claude\commands\enhance-claude-md\

docs/QUICK_START.md

@@ -256,7 +256,7 @@ Claude, invoke claude-md-guardian to update CLAUDE.md
 
 ### Tip 1: Use Modular Architecture for Large Projects
 
-If your CLAUDE.md exceeds 300 lines, split it:
+If your CLAUDE.md approaches or exceeds the 150-line cap, split it (or run `/sync-claude-md` to split for you):
 
 ```bash
 /enhance-claude-md

docs/TROUBLESHOOTING.md

@@ -29,7 +29,7 @@ Common issues and solutions for ClaudeForge.
 2. **Verify installation paths:**
    ```bash
    # macOS/Linux
-   ls -la ~/.claude/commands/enhance-claude-md/
+   ls -la ~/.claude/commands/enhance-claude-md.md ~/.claude/commands/sync-claude-md.md
    ls -la ~/.claude/skills/claudeforge-skill/
    ls -la ~/.claude/agents/claude-md-guardian.md
 
@@ -119,7 +119,7 @@ Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass
 2. **Check file length:**
    ```bash
    wc -l CLAUDE.md
-   # Recommended: 20-300 lines
+   # Hard cap: 150 lines. Sweet spot: 50-120.
    # If > 300: Consider modular architecture
    ```
 
@@ -173,7 +173,7 @@ Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass
 
 **Symptoms:**
 - Single CLAUDE.md generated for large project
-- File exceeds 300 lines
+- File exceeds the 150-line cap (validator hook will surface this)
 
 **Causes:**
 - Project type not detected as `fullstack`

examples/integration-examples.md

@@ -56,8 +56,8 @@ if [ -f "CLAUDE.md" ]; then
 
     # Check file length
     lines=$(wc -l < CLAUDE.md)
-    if [ $lines -lt 20 ] || [ $lines -gt 400 ]; then
-        echo "Error: CLAUDE.md length ($lines lines) outside recommended range (20-300)"
+    if [ $lines -lt 20 ] || [ $lines -gt 150 ]; then
+        echo "Error: CLAUDE.md length ($lines lines) outside the 20-150 cap; run /sync-claude-md to split."
         exit 1
     fi
 

examples/modular-setup.md

@@ -8,7 +8,7 @@ Examples of modular CLAUDE.md structure for large projects.
 
 - Full-stack projects with distinct frontend/backend
 - Team size > 10 developers
-- Single CLAUDE.md would exceed 300 lines
+- Single CLAUDE.md would exceed the 150-line cap
 - Different teams own different areas
 
 ---

install.ps1

@@ -178,6 +178,9 @@ Write-Host ""
 Write-Info "Installation will create:"
 Write-Host "  • Skill:    $skillsDir\claudeforge-skill\"
 Write-Host "  • Skill:    $skillsDir\karpathy-guidelines\"
+Write-Host "  • Skill:    $skillsDir\claude-md-drift-audit\"
+Write-Host "  • Skill:    $skillsDir\claude-md-link-check\"
+Write-Host "  • Skill:    $skillsDir\claude-md-dependency-rescan\"
 Write-Host "  • Command:  $commandsDir\enhance-claude-md.md"
 Write-Host "  • Command:  $commandsDir\sync-claude-md.md"
 Write-Host "  • Agent:    $agentsDir\claude-md-guardian.md"
@@ -232,6 +235,25 @@ if (Test-Path $nestedKarpathy) {
 }
 Write-Success "Karpathy guidelines installed → $karpathyPath\"
 
+# Install the forked task-style audit skills as separate top-level skills
+# so each is invocable standalone and discoverable by /sync-claude-md --weekly.
+$auditSkills = @("claude-md-drift-audit", "claude-md-link-check", "claude-md-dependency-rescan")
+foreach ($auditSkill in $auditSkills) {
+    Write-Info "Installing $auditSkill skill..."
+    $auditTarget = "$skillsDir\$auditSkill"
+    if (Test-Path $auditTarget) {
+        Write-Warning "Existing $auditSkill skill found. Creating backup..."
+        $backupName = "$auditSkill.backup.$(Get-Date -Format 'yyyyMMdd_HHmmss')"
+        Move-Item -Path $auditTarget -Destination "$skillsDir\$backupName" -Force
+    }
+    Copy-Item -Path "skill\$auditSkill" -Destination $auditTarget -Recurse -Force
+    $nestedAudit = "$skillPath\$auditSkill"
+    if (Test-Path $nestedAudit) {
+        Remove-Item -Path $nestedAudit -Recurse -Force
+    }
+    Write-Success "$auditSkill installed → $auditTarget\"
+}
+
 # Install slash commands. Each .md file in command/ becomes its own
 # top-level command file so it registers as /<name>. README.md is skipped.
 Write-Info "Installing slash commands..."
@@ -376,12 +398,18 @@ Write-Host ""
 if ($scope -eq "user-level") {
     Write-Host "  Remove-Item -Recurse -Force ~\.claude\skills\claudeforge-skill"
     Write-Host "  Remove-Item -Recurse -Force ~\.claude\skills\karpathy-guidelines"
+    Write-Host "  Remove-Item -Recurse -Force ~\.claude\skills\claude-md-drift-audit"
+    Write-Host "  Remove-Item -Recurse -Force ~\.claude\skills\claude-md-link-check"
+    Write-Host "  Remove-Item -Recurse -Force ~\.claude\skills\claude-md-dependency-rescan"
     Write-Host "  Remove-Item -Force ~\.claude\commands\enhance-claude-md.md"
     Write-Host "  Remove-Item -Force ~\.claude\commands\sync-claude-md.md"
     Write-Host "  Remove-Item -Force ~\.claude\agents\claude-md-guardian.md"
 } else {
     Write-Host "  Remove-Item -Recurse -Force .\.claude\skills\claudeforge-skill"
     Write-Host "  Remove-Item -Recurse -Force .\.claude\skills\karpathy-guidelines"
+    Write-Host "  Remove-Item -Recurse -Force .\.claude\skills\claude-md-drift-audit"
+    Write-Host "  Remove-Item -Recurse -Force .\.claude\skills\claude-md-link-check"
+    Write-Host "  Remove-Item -Recurse -Force .\.claude\skills\claude-md-dependency-rescan"
     Write-Host "  Remove-Item -Force .\.claude\commands\enhance-claude-md.md"
     Write-Host "  Remove-Item -Force .\.claude\commands\sync-claude-md.md"
     Write-Host "  Remove-Item -Force .\.claude\agents\claude-md-guardian.md"

install.sh

@@ -159,6 +159,9 @@ echo ""
 print_info "Installation will create:"
 echo "  • Skill:    $SKILLS_DIR/claudeforge-skill/"
 echo "  • Skill:    $SKILLS_DIR/karpathy-guidelines/"
+echo "  • Skill:    $SKILLS_DIR/claude-md-drift-audit/"
+echo "  • Skill:    $SKILLS_DIR/claude-md-link-check/"
+echo "  • Skill:    $SKILLS_DIR/claude-md-dependency-rescan/"
 echo "  • Command:  $COMMANDS_DIR/enhance-claude-md.md"
 echo "  • Command:  $COMMANDS_DIR/sync-claude-md.md"
 echo "  • Agent:    $AGENTS_DIR/claude-md-guardian.md"
@@ -204,6 +207,21 @@ cp -r skill/karpathy-guidelines "$SKILLS_DIR/karpathy-guidelines"
 rm -rf "$SKILLS_DIR/claudeforge-skill/karpathy-guidelines"
 print_success "Karpathy guidelines installed → $SKILLS_DIR/karpathy-guidelines/"
 
+# Install the forked task-style audit skills as separate top-level skills
+# so each is invocable standalone (/claude-md-drift-audit etc.) and
+# discoverable by /sync-claude-md --weekly.
+for audit_skill in claude-md-drift-audit claude-md-link-check claude-md-dependency-rescan; do
+    print_info "Installing $audit_skill skill..."
+    audit_target="$SKILLS_DIR/$audit_skill"
+    if [ -d "$audit_target" ]; then
+        print_warning "Existing $audit_skill skill found. Creating backup..."
+        mv "$audit_target" "$audit_target.backup.$(date +%Y%m%d_%H%M%S)"
+    fi
+    cp -r "skill/$audit_skill" "$audit_target"
+    rm -rf "$SKILLS_DIR/claudeforge-skill/$audit_skill"
+    print_success "$audit_skill installed → $audit_target/"
+done
+
 # Install slash commands. Each .md file in command/ is installed as its own
 # top-level command file so it registers as /<name> rather than as a nested
 # /<dir>:<name>. README.md and other non-command files are skipped.
@@ -337,12 +355,18 @@ echo ""
 if [ "$SCOPE" == "user-level" ]; then
     echo "  rm -rf ~/.claude/skills/claudeforge-skill"
     echo "  rm -rf ~/.claude/skills/karpathy-guidelines"
+    echo "  rm -rf ~/.claude/skills/claude-md-drift-audit"
+    echo "  rm -rf ~/.claude/skills/claude-md-link-check"
+    echo "  rm -rf ~/.claude/skills/claude-md-dependency-rescan"
     echo "  rm -f  ~/.claude/commands/enhance-claude-md.md"
     echo "  rm -f  ~/.claude/commands/sync-claude-md.md"
     echo "  rm -f ~/.claude/agents/claude-md-guardian.md"
 else
     echo "  rm -rf ./.claude/skills/claudeforge-skill"
     echo "  rm -rf ./.claude/skills/karpathy-guidelines"
+    echo "  rm -rf ./.claude/skills/claude-md-drift-audit"
+    echo "  rm -rf ./.claude/skills/claude-md-link-check"
+    echo "  rm -rf ./.claude/skills/claude-md-dependency-rescan"
     echo "  rm -f  ./.claude/commands/enhance-claude-md.md"
     echo "  rm -f  ./.claude/commands/sync-claude-md.md"
     echo "  rm -f ./.claude/agents/claude-md-guardian.md"