Agent skill

Init Deep

by AkaraChen in AkaraChen/aghub

Generate hierarchical AGENTS.md and ensure paired CLAUDE.md files for codebases.

MITAuto-check passedAgent Workflows

Install Init Deep

skills CLI
$ npx skills add AkaraChen/aghub --skill init-deep -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install AkaraChen/aghub init-deep --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/AkaraChen/aghub.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/init-deep .claude/skills/init-deep && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
init-deep
GitHub stars
272
Token cost
~3.6k tokens
SKILL.md length
766 words
Files
1
Skills in repo
2
Repo updated
First seen
Licence
MIT

At a glance

Generate hierarchical AGENTS.md and ensure paired CLAUDE.md files for codebases.

  • Works in 4 steps: Discovery + Analysis (Concurrent) → Scoring & Location Decision → Generate AGENTS.md & CLAUDE.md → …
  • User asks to generate AGENTS.md files
  • SKILL.md covers Usage, Workflow (High-Level), Phase 1: Discovery + Analysis… and Phase 2: Scoring & Location…, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Init Deep is an agent skill from AkaraChen/aghub. Generate hierarchical AGENTS.md and ensure paired CLAUDE.md files for codebases. Creates root AGENTS.md + CLAUDE.md plus complexity-scored subdirectory files. Use when user asks to "generate AGENTS.md files", "create codebase knowledge base", "run /init-deep", or wants comprehensive project documentation. Supports update mode (default) and --create-new flag to regenerate from scratch.

Its SKILL.md is about 3.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows, covering Agent instruction files. It works with Bash and Model Context Protocol. The repository describes itself as: One hub for every AI coding agent. Unified configuration management for 22+ assistants. The licence is MIT.

When your agent uses it

  • User asks to generate AGENTS.md files
  • Create codebase knowledge base
  • Wants comprehensive project documentation

Example prompts

  • “generate AGENTS.md files”
  • “create codebase knowledge base”
  • “run /init-deep”
  • “/init-deep”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Discovery + Analysis (Concurrent)
  2. Scoring & Location Decision
  3. Generate AGENTS.md & CLAUDE.md
  4. Review & Deduplicate

What it can do on your machine

Read from SKILL.md and the folder at commit 61a7ee7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash and markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Init Deep loads about 3.6k tokens when it runs. Until then it costs about 99 tokens; SKILL.md has 766 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~99
When it runs · the whole SKILL.md, loaded when a task matches
~3.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from AkaraChen/aghub at commit 61a7ee7, republished under its MIT licence (© AkaraChen). 766 words, ~3,642 tokens.

Download SKILL.mdSave it as .claude/skills/init-deep/SKILL.md (or your agent's skills folder).
name
init-deep
description
Generate hierarchical AGENTS.md and ensure paired CLAUDE.md files for codebases. Creates root AGENTS.md + CLAUDE.md plus complexity-scored subdirectory files. Use when user asks to "generate AGENTS.md files", "create codebase knowledge base", "run /init-deep", or wants comprehensive project documentation. Supports update mode (default) and --create-new flag to regenerate from scratch.

/init-deep

Generate hierarchical AGENTS.md files. Ensure every AGENTS.md has a paired CLAUDE.md (and vice versa) via symlinks. Root + complexity-scored subdirectories + all monorepo packages.

Usage

/init-deep                      # Update mode: modify existing + create new where warranted
/init-deep --create-new         # Read existing → remove all → regenerate from scratch
/init-deep --max-depth=2        # Limit directory depth (default: 3)

Workflow (High-Level)

  1. Discovery + Analysis (concurrent)
    • Fire background explore agents immediately
    • Main session: bash structure + LSP codemap + read existing AGENTS.md and CLAUDE.md
  2. Score & Decide - Determine AGENTS.md/CLAUDE.md locations from merged findings
  3. Generate - Root first, then subdirs in parallel
  4. Review - Deduplicate, trim, validate, ensure pairs
<critical>
**TodoWrite ALL phases. Mark in_progress → completed in real-time.**
```
TodoWrite([
  { id: "discovery", content: "Fire explore agents + LSP codemap + read existing AGENTS.md and CLAUDE.md", status: "pending", priority: "high" },
  { id: "scoring", content: "Score directories, determine locations + monorepo packages", status: "pending", priority: "high" },
  { id: "generate", content: "Generate AGENTS.md + CLAUDE.md files (root + subdirs)", status: "pending", priority: "high" },
  { id: "review", content: "Deduplicate, validate, trim, ensure file pairs", status: "pending", priority: "medium" }
])
```
</critical>

Phase 1: Discovery + Analysis (Concurrent)

Mark "discovery" as in_progress.

Fire Background Explore Agents IMMEDIATELY

Don't wait—these run async while main session works.

// Fire all at once, collect results later
task(subagent_type="explore", load_skills=[], description="Explore project structure", run_in_background=true, prompt="Project structure: PREDICT standard patterns for detected language → REPORT deviations only")
task(subagent_type="explore", load_skills=[], description="Find entry points", run_in_background=true, prompt="Entry points: FIND main files → REPORT non-standard organization")
task(subagent_type="explore", load_skills=[], description="Find conventions", run_in_background=true, prompt="Conventions: FIND config files (.eslintrc, pyproject.toml, .editorconfig) → REPORT project-specific rules")
task(subagent_type="explore", load_skills=[], description="Find anti-patterns", run_in_background=true, prompt="Anti-patterns: FIND 'DO NOT', 'NEVER', 'ALWAYS', 'DEPRECATED' comments → LIST forbidden patterns")
task(subagent_type="explore", load_skills=[], description="Explore build/CI", run_in_background=true, prompt="Build/CI: FIND .github/workflows, Makefile → REPORT non-standard patterns")
task(subagent_type="explore", load_skills=[], description="Find test patterns", run_in_background=true, prompt="Test patterns: FIND test configs, test structure → REPORT unique conventions")
<dynamic-agents>
**DYNAMIC AGENT SPAWNING**: After bash analysis, spawn ADDITIONAL explore agents based on project scale:
FactorThresholdAdditional Agents
Total files>100+1 per 100 files
Total lines>10k+1 per 10k lines
Directory depth≥4+2 for deep exploration
Large files (>500 lines)>10 files+1 for complexity hotspots
Monorepodetected+1 per package/workspace
Multiple languages>1+1 per language
bash
# Measure project scale first
total_files=$(find . -type f -not -path '*/node_modules/*' -not -path '*/.git/*' | wc -l)
total_lines=$(find . -type f \( -name "*.ts" -o -name "*.py" -o -name "*.go" \) -not -path '*/node_modules/*' -exec wc -l {} + 2>/dev/null | tail -1 | awk '{print $1}')
large_files=$(find . -type f \( -name "*.ts" -o -name "*.py" \) -not -path '*/node_modules/*' -exec wc -l {} + 2>/dev/null | awk '$1 > 500 {count++} END {print count+0}')
max_depth=$(find . -type d -not -path '*/node_modules/*' -not -path '*/.git/*' | awk -F/ '{print NF}' | sort -rn | head -1)

Example spawning:

// 500 files, 50k lines, depth 6, 15 large files → spawn 5+5+2+1 = 13 additional agents
task(subagent_type="explore", load_skills=[], description="Analyze large files", run_in_background=true, prompt="Large file analysis: FIND files >500 lines, REPORT complexity hotspots")
task(subagent_type="explore", load_skills=[], description="Explore deep modules", run_in_background=true, prompt="Deep modules at depth 4+: FIND hidden patterns, internal conventions")
task(subagent_type="explore", load_skills=[], description="Find shared utilities", run_in_background=true, prompt="Cross-cutting concerns: FIND shared utilities across directories")
// ... more based on calculation
</dynamic-agents>
Main Session: Concurrent Analysis

While background agents run, main session does:

1. Bash Structural Analysis
bash
# Directory depth + file counts
find . -type d -not -path '*/\.*' -not -path '*/node_modules/*' -not -path '*/venv/*' -not -path '*/dist/*' -not -path '*/build/*' | awk -F/ '{print NF-1}' | sort -n | uniq -c

# Files per directory (top 30)
find . -type f -not -path '*/\.*' -not -path '*/node_modules/*' | sed 's|/[^/]*$||' | sort | uniq -c | sort -rn | head -30

# Code concentration by extension
find . -type f \( -name "*.py" -o -name "*.ts" -o -name "*.tsx" -o -name "*.js" -o -name "*.go" -o -name "*.rs" \) -not -path '*/node_modules/*' | sed 's|/[^/]*$||' | sort | uniq -c | sort -rn | head -20

# Existing AGENTS.md / CLAUDE.md
find . -type f \( -name "AGENTS.md" -o -name "CLAUDE.md" \) -not -path '*/node_modules/*' 2>/dev/null

# Monorepo detection (package directories)
find . \( -name "package.json" -o -name "pyproject.toml" -o -name "Cargo.toml" -o -name "go.mod" \) -not -path '*/node_modules/*' -not -path '*/.git/*' | sed 's|/[^/]*$||' | sort | uniq
2. Read Existing AGENTS.md and CLAUDE.md

For each directory where either AGENTS.md or CLAUDE.md exists:

agents_exists = file exists at {dir}/AGENTS.md
claude_exists = file exists at {dir}/CLAUDE.md

If agents_exists AND claude_exists:
  Read both files
  Merge their contents into EXISTING_AGENTS map for that directory
Else if agents_exists AND NOT claude_exists:
  Read AGENTS.md
  Create symlink: ln -s AGENTS.md CLAUDE.md (or ln -s CLAUDE.md AGENTS.md if you prefer; standard: ln -s AGENTS.md CLAUDE.md)
Else if claude_exists AND NOT agents_exists:
  Read CLAUDE.md
  Create symlink: ln -s CLAUDE.md AGENTS.md
<critical>
If `--create-new`: Read all existing first (preserve context) → delete all AGENTS.md and CLAUDE.md + their symlinks → regenerate.
</critical>
3. LSP Codemap (if available)
LspServers()  # Check availability

# Entry points (parallel)
LspDocumentSymbols(filePath="src/index.ts")
LspDocumentSymbols(filePath="main.py")

# Key symbols (parallel)
LspWorkspaceSymbols(filePath=".", query="class")
LspWorkspaceSymbols(filePath=".", query="interface")
LspWorkspaceSymbols(filePath=".", query="function")

# Centrality for top exports
LspFindReferences(filePath="...", line=X, character=Y)

LSP Fallback: If unavailable, rely on explore agents + AST-grep.

Collect Background Results
// After main session analysis done, collect all task results
for each task_id: background_output(task_id="...")

Merge: bash + LSP + existing + explore findings. Mark "discovery" as completed.


Phase 2: Scoring & Location Decision

Mark "scoring" as in_progress.

Scoring Matrix
FactorWeightHigh ThresholdSource
File count3x>20bash
Subdir count2x>5bash
Code ratio2x>70%bash
Unique patterns1xHas own configexplore
Module boundary2xHas index.ts/init.pybash
Symbol density2x>30 symbolsLSP
Export count2x>10 exportsLSP
Reference centrality3x>20 refsLSP
Monorepo Rule

Every monorepo package directory MUST have an AGENTS.md + CLAUDE.md pair, regardless of score.

Detect packages via:

  • package.json in subdirectories (Node/Yarn/npm workspaces, pnpm)
  • pyproject.toml with [tool.poetry] or [project]
  • Cargo.toml (Rust workspace member)
  • go.mod (Go module)

Add all unique package directories to AGENTS_LOCATIONS with type: "package".

Decision Rules
ScoreAction
Root (.)ALWAYS create
Monorepo packageALWAYS create
>15Create AGENTS.md + CLAUDE.md
8-15Create if distinct domain
<8Skip (parent covers)
Output
AGENTS_LOCATIONS = [
  { path: ".", type: "root" },
  { path: "packages/core", type: "package", score: null, reason: "monorepo package" },
  { path: "src/hooks", score: 18, reason: "high complexity" },
  { path: "src/api", score: 12, reason: "distinct domain" }
]

Mark "scoring" as completed.


Phase 3: Generate AGENTS.md & CLAUDE.md

Mark "generate" as in_progress.

<critical>
**File Writing Rule**:
- If AGENTS.md already exists at the target path → use `Edit` tool.
- If AGENTS.md does NOT exist → use `Write` tool.
- NEVER use Write to overwrite an existing file. ALWAYS check existence first via `Read` or discovery results.
- After writing AGENTS.md, ensure CLAUDE.md exists in the same directory. If missing, create it as a symlink to AGENTS.md.
- If both files already exist and both are regular files (not symlinks), merge their content mentally and then use `Edit` to update both to the merged content.
</critical>
Show full SKILL.md (292 more words)Show less
Pairing Rules Per Directory

For every location in AGENTS_LOCATIONS:

  1. Generate AGENTS.md content using the templates below.
  2. Ensure CLAUDE.md exists in the same directory:
    • If neither exists: Write AGENTS.md, then ln -s AGENTS.md CLAUDE.md
    • If only AGENTS.md exists: ln -s AGENTS.md CLAUDE.md
    • If only CLAUDE.md exists: mv CLAUDE.md AGENTS.md, then ln -s AGENTS.md CLAUDE.md
    • If both exist as regular files: Merge content from both, then use Edit to update both to the merged content.

Preferred approach: Write AGENTS.md as the canonical file, then ln -s AGENTS.md CLAUDE.md in all cases where no conflict exists.

Root AGENTS.md (Full Treatment)
markdown
# PROJECT KNOWLEDGE BASE

**Generated:** {TIMESTAMP}
**Commit:** {SHORT_SHA}
**Branch:** {BRANCH}

## OVERVIEW

{1-2 sentences: what + core stack}

## STRUCTURE

{root}/ ├── {dir}/ # {non-obvious purpose only} └── {entry}

## WHERE TO LOOK
| Task | Location | Notes |
|------|----------|-------|

## CODE MAP
{From LSP - skip if unavailable or project <10 files}

| Symbol | Type | Location | Refs | Role |
|--------|------|----------|------|------|

## CONVENTIONS
{ONLY deviations from standard}

## ANTI-PATTERNS (THIS PROJECT)
{Explicitly forbidden here}

## UNIQUE STYLES
{Project-specific}

## COMMANDS

{dev/test/build}

## NOTES
{Gotchas}

Quality gates: 50-150 lines, no generic advice, no obvious info.

Monorepo Package AGENTS.md

Same structure as root but scoped to the package:

  • Mention package name and its role in the monorepo
  • Link to root AGENTS.md for global conventions
  • 30-80 lines max
Subdirectory AGENTS.md (Parallel)

Launch writing tasks for each location:

for loc in AGENTS_LOCATIONS (except root):
  task(category="writing", load_skills=[], run_in_background=false, description="Generate AGENTS.md", prompt=`
    Generate AGENTS.md for: ${loc.path}
    - Type: ${loc.type} (package | subdir)
    - Reason: ${loc.reason}
    - 30-80 lines max
    - NEVER repeat parent content
    - Sections: OVERVIEW (1 line), STRUCTURE (if >5 subdirs), WHERE TO LOOK, CONVENTIONS (if different), ANTI-PATTERNS
    If type is "package", include the package's role in the monorepo and link to root conventions.
  `)

After each AGENTS.md is written, run the pairing check to ensure CLAUDE.md exists (create symlink if missing).

Wait for all. Mark "generate" as completed.


Phase 4: Review & Deduplicate

Mark "review" as in_progress.

For each generated file:

  • Remove generic advice
  • Remove parent duplicates
  • Trim to size limits
  • Verify telegraphic style
  • Verify every AGENTS.md has a paired CLAUDE.md in the same directory
  • Fix any missing symlinks

Mark "review" as completed.


Final Report

=== init-deep Complete ===

Mode: {update | create-new}

Files:
  [OK] ./AGENTS.md (root, {N} lines)
  [OK] ./CLAUDE.md → symlinked to ./AGENTS.md
  [OK] ./packages/core/AGENTS.md ({N} lines)
  [OK] ./packages/core/CLAUDE.md → symlinked to ./AGENTS.md
  [OK] ./src/hooks/AGENTS.md ({N} lines)
  [OK] ./src/hooks/CLAUDE.md → symlinked to ./AGENTS.md

Dirs Analyzed: {N}
AGENTS.md Created: {N}
CLAUDE.md Created: {N}
Pairs Ensured: {N}

Hierarchy:
  ./AGENTS.md
  ├── packages/core/AGENTS.md
  └── src/hooks/AGENTS.md

Anti-Patterns

  • Static agent count: MUST vary agents based on project size/depth
  • Sequential execution: MUST parallel (explore + LSP concurrent)
  • Ignoring existing: ALWAYS read existing first, even with --create-new
  • Over-documenting: Not every dir needs AGENTS.md (except monorepo packages)
  • Redundancy: Child never repeats parent
  • Generic content: Remove anything that applies to ALL projects
  • Verbose style: Telegraphic or die
  • Orphan files: NEVER leave AGENTS.md without CLAUDE.md in the same directory

© AkaraChen, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/init-deep of AkaraChen/aghub.

Open the folder on GitHubat commit 61a7ee7

Compare with similar skills

Init Deep next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Init Deep compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Init Deep this skillAkaraChen/aghub272—~3.6kAutomated safety check: PassMIT
Memory Mapmajiayu000/claude-skill-registry6661 repos~3.8kAutomated safety check: PassMIT
Env Setupmajiayu000/claude-skill-registry6661 repos~1.7kAutomated safety check: NotesMIT
Neat-Freak Knowledge CloseoutKKKKhazix/khazix-skills21k—~1.9kAutomated safety check: PassMIT
Crush Configurationcharmbracelet/crush29k—~3.7kAutomated safety check: PassCustom licence
Agent Setup Health Audittw93/Waza7.2k—~5.2kAutomated safety check: NotesMIT

Similar skills

  • Memory Map

    majiayu000/claude-skill-registry

    A skill your agent uses when installing or configuring memorymap, writing CLAUDE.md session-setup instructions, choosing what to save in memory vs history, managing or pruning history chunks, using…

    666 GitHub starsUsed in 1 repo~3.8k tokens
    Agent WorkflowsAuto-check passed
  • Env Setup

    majiayu000/claude-skill-registry

    Claude Code 环境一键同步工具。从 GitHub 仓库同步所有配置到本地:output-styles 风格、CLAUDE.md 全局提示词、MCP 服务器配置、Agent 配置、Plugin 配置。适用于多设备统一环境、换电脑恢复、团队共享配置等场景。当用户需要从 GitHub 仓库同步 Claude Code/OpenClaw 环境配置时使用此 skill。

    666 GitHub starsUsed in 1 repo~1.7k tokens
    Agent WorkflowsAuto-check: notes
  • Neat-Freak Knowledge Closeout

    KKKKhazix/khazix-skills

    Brings project docs, agent rule files, authorized memory and leftover workspace files back in line with what the code and runtime actually do at the end of a work session.

    21k GitHub stars~1.9k tokensUpdated 6 days ago
    Agent WorkflowsAuto-check passed
  • Crush Configuration

    charmbracelet/crush

    Explains how to configure the Crush coding agent with crushrc or crush.json, covering providers, models, LSPs, MCP servers, hooks, permissions and config precedence.

    29k GitHub stars~3.7k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Audits a project's agent configuration, instruction drift, hooks, MCP and AI maintainability, then reports prioritized findings with evidence and next actions.

    7.2k GitHub stars~5.2k tokensUpdated yesterday
    Agent WorkflowsAuto-check: notes
  • Record Demo

    apify/mcpc

    Official

    Record or regenerate the mcpc demo GIFs (the README hero docs/images/mcpc-demo.gif and the focused tapes in docs/vhs/) with VHS.

    983 GitHub stars~3.3k tokensUpdated today
    Agent WorkflowsAuto-check: notes

More from AkaraChen/aghub

  • Project Form Patterns

    AkaraChen/aghub

    Form implementation guidance for the aghub desktop app. An agent skill from AkaraChen/aghub.

    272 GitHub stars~1.1k tokensUpdated 2 days ago
    Auto-check passed

Categories

Questions about Init Deep

What does Init Deep do?

Generate hierarchical AGENTS.md and ensure paired CLAUDE.md files for codebases. Init Deep is an agent skill from AkaraChen/aghub.md files for codebases.

When should I use Init Deep?

Init Deep fits situations like: user asks to generate AGENTS.md files; create codebase knowledge base; wants comprehensive project documentation.

How do I install Init Deep in Claude Code?

Run `npx skills add AkaraChen/aghub --skill init-deep -a claude-code`. Or copy the skill folder (.claude/skills/init-deep in AkaraChen/aghub) into .claude/skills/init-deep in your project. Claude Code loads it when a task matches its description.

How do I install Init Deep in Codex?

Run `npx skills add AkaraChen/aghub --skill init-deep -a codex`. Or copy the skill folder (.claude/skills/init-deep in AkaraChen/aghub) into .agents/skills/init-deep in your project. Codex loads it when a task matches its description.

Can I use Init Deep in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add AkaraChen/aghub --skill init-deep -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/init-deep, .gemini/skills/init-deep, .github/skills/init-deep and .opencode/skills/init-deep in your project.

What does Init Deep need to run?

SKILL.md names no scripts, command-line tools or credentials: Init Deep is instructions for the agent only.

Does Init Deep access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Init Deep safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Init Deep use?

Init Deep is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Init Deep use?

About 3.6k tokens (SKILL.md is roughly 15k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Init Deep?

Skills that share tags, products or a category with Init Deep: Memory Map (majiayu000/claude-skill-registry, 666 stars), Env Setup (majiayu000/claude-skill-registry, 666 stars), Neat-Freak Knowledge Closeout (KKKKhazix/khazix-skills, 21k stars) and Crush Configuration (charmbracelet/crush, 29k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Init Deep?

AkaraChen (a GitHub user) maintains it in AkaraChen/aghub, which has 272 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 5, 2026.

Source: AkaraChen/aghub on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.