Agents Rock — Development skill for Claude Code

agents-rock

A Claude Code plugin marketplace.

Install

/plugin marketplace add git@github.com:v11g/agents-rock.git

(HTTPS equivalent: `https://github.com/v11g/agents-rock.git`)

/plugin install @agents-rock

Replace `` with any plugin from the table below, e.g. `/plugin install lmk@agents-rock`.

Install via npx (Claude Code + Codex)

npx @v11g/agents-rock                                   # interactive: pick plugins, agents, scope
npx @v11g/agents-rock -p  -a claude --project   # this project, Claude Code
npx @v11g/agents-rock -p  -a codex --global     # your home dir, Codex
npx @v11g/agents-rock -p  -a claude -a codex -g # both agents, home dir
npx @v11g/agents-rock uninstall -p  --project   # remove from this project, all agents

`-p ` installs every skill that plugin ships.

Run with no options and you get prompts for plugins, agents, and scope, then a summary to confirm before anything is written. Nothing is written until you confirm.

Scope

Flag	Where skills land	Good for
--project	the detected project root	skills committed alongside one repo
--global / -g	your home directory	skills you want in every project

`--project` walks up from the current directory looking for `.git`, then for `package.json`, `pyproject.toml`, `go.mod`, or `Cargo.toml`. When the root it finds is not the directory you are standing in, it shows you both and asks which to use — so running the installer from `packages/web/src` does not quietly create a skills directory there. Use `--dir ` to name the directory yourself and skip detection.

`--global` honors `CLAUDE_CONFIG_DIR` and `CODEX_HOME` if you have relocated either agent's config.

Layout

Both scopes use the same shape — one canonical copy, symlinked per agent:

project scope                        user scope
/.agents/skills/        ~/.agents/skills/