claude-mods

claude-mods

Custom commands, skills, and agents for Claude Code.

Structure

claude-mods/
├── commands/           # Slash commands
├── skills/             # Custom skills
├── agents/             # Custom subagents
├── install.sh          # Linux/macOS installer
└── install.ps1         # Windows installer

Installation

Quick Install

Linux/macOS:

git clone --recursive https://github.com/0xDarkMatter/claude-mods.git
cd claude-mods
./install.sh

Windows (PowerShell):

git clone --recursive https://github.com/0xDarkMatter/claude-mods.git
cd claude-mods
.\install.ps1

Manual Install

Clone with submodules:

git clone --recursive https://github.com/0xDarkMatter/claude-mods.git

Then symlink or copy to your Claude directories:

• Commands → ~/.claude/commands/
• Skills → ~/.claude/skills/
• Agents → ~/.claude/agents/

What's Included

Commands

Command	Description
g-slave	Dispatch Gemini CLI to analyze large codebases. Gemini does the grunt work, Claude gets the summary.
agent-genesis	Generate Claude Code expert agent prompts for any technology platform.
save	Save session state before ending. Creates claude-state.json and claude-progress.md for session continuity.
load	Load session context from saved state. Shows what changed, suggests next action.
plan	Create and persist project plans. Captures Plan Mode state and writes to git-trackable PLAN.md.
review	Code review staged changes or specific files. Analyzes bugs, security, performance, style.
test	Generate tests with automatic framework detection (Jest, Vitest, pytest, etc.).
explain	Deep explanation of complex code, files, or concepts. Architecture, data flow, design decisions.

Skills

Skill	Description
agent-discovery	Analyze tasks and recommend specialized agents
code-stats	Analyze codebase with tokei and difft
data-processing	Process JSON with jq, YAML/TOML with yq
git-workflow	Enhanced git operations with lazygit, gh, delta
project-docs	Scan and synthesize project documentation
python-env	Fast Python environment management with uv
safe-file-reader	Read files without permission prompts
structural-search	Search code by AST structure with ast-grep
task-runner	Run project commands with just

Agents

Agent	Description
astro-expert	Astro projects, SSR/SSG, Cloudflare deployment
asus-router-expert	Asus routers, network hardening, Asuswrt-Merlin
aws-fargate-ecs-expert	Amazon ECS on Fargate, container deployment
bash-expert	Defensive Bash scripting, CI/CD pipelines
cloudflare-expert	Cloudflare Workers, Pages, DNS, security
craftcms-expert	Craft CMS content modeling, Twig, plugins, GraphQL
cypress-expert	Cypress E2E and component testing, custom commands, CI/CD
fetch-expert	Parallel web fetching with retry logic
firecrawl-expert	Web scraping, crawling, structured extraction
javascript-expert	Modern JavaScript, async patterns, optimization
laravel-expert	Laravel framework, Eloquent, testing
react-expert	React hooks, state management, Server Components, performance
typescript-expert	TypeScript type system, generics, utility types, strict mode
vue-expert	Vue 3, Composition API, Pinia state management, performance
payloadcms-expert	Payload CMS architecture and configuration
playwright-roulette-expert	Playwright automation for casino testing
postgres-expert	PostgreSQL management and optimization
project-organizer	Reorganize directory structures, cleanup
python-expert	Advanced Python, testing, optimization
rest-expert	RESTful API design, HTTP methods, status codes
sql-expert	Complex SQL queries, optimization, indexing
tailwind-expert	Tailwind CSS, responsive design
wrangler-expert	Cloudflare Workers deployment, wrangler.toml

Session Continuity: /save + /load

These commands fill a gap in Claude Code's native session management.

The problem: Claude Code's --resume flag restores conversation history, but TodoWrite task state does not persist between sessions—by design. Claude Code treats each session as isolated; the philosophy is that persistent state belongs in files you control.

TodoWrite tasks are stored at ~/.claude/todos/[session-id].json and deleted when the session ends. This is intentional.

The solution: /save and /load implement the pattern from Anthropic's Effective Harnesses for Long-Running Agents:

"Every subsequent session asks the model to make incremental progress, then leave structured updates."

What Persists vs What Doesn't

Claude Code Feature	Persists?	Location
Conversation history	Yes	Internal (use --resume)
CLAUDE.md context	Yes	./CLAUDE.md
TodoWrite tasks	No	Deleted on session end
Plan Mode state	No	In-memory only

How /save + /load Works

Session 1:
  [work on tasks]
  /save "Stopped at auth module"    # Writes .claude/claude-state.json + claude-progress.md

Session 2:
  /load                              # Restores TodoWrite, shows git diff, suggests next action
  → "In progress: Auth module refactor"
  → "Notes: Stopped at auth module"

Why Not Just Use --resume?

Feature	--resume	/save + /load
Conversation history	Yes	No
TodoWrite tasks	No	Yes
Git context	No	Yes
Human-readable summary	No	Yes
Git-trackable	No	Yes
Works across machines	No	Yes (if committed)
Team sharing	No	Yes

Use both together: claude --resume for conversation context, /load for task state.

Updating

Pull updates including submodules:

git pull --recurse-submodules
git submodule update --remote

Then re-run the install script.

License

MIT

---

Extend Claude Code. Your way.