Agents Config — DevOps skill for Claude Code

agents-config

Lorenzo Graizzaro's **agent config + skills hub**, built to be portable: one repo that configures every coding AI anyone uses (Claude Code, Codex CLI, Cursor, Google Antigravity/Gemini) the same way, plus the on-demand skill library they all share. Clone it and point your own agent at it — personal content (names, paths, learning stage, GitHub owner) lives only in `config/profiles/.md`, never in the shared files.

Two things live here, and they're both "always available, loaded only when needed":

• Config (config/) — instructions, path-scoped rules, lifecycle hooks, and the three model-pinned subagents. Generated/symlinked into ~/.claude/ and ~/.codex/ by install.sh.
• Skills (category directories below) — SKILL.md files loaded on demand when their description matches the task, mirrored flat into ~/.claude/skills by sync.sh.

Neither of these makes a project well-run on its own — see ["How it works"](#how-it-works) for the second, per-project layer (`project-init`) that does the actual enforcement.

Install

Pick **one** method per machine — they overlap and aren't meant to be combined.

Method 1 — `install.sh` (full: config + rules + hooks + subagents + skills)

git clone https://github.com/LorenGrz/agents-config ~/.agents/skills
~/.agents/skills/install.sh --dry-run    # preview, changes nothing
~/.agents/skills/install.sh --profile 

Inside a Claude Code or Codex session opened in the clone, you can instead just ask your agent to "install this repo" — see `AGENTS.md` and the `agents-config-setup` skill, which implement the same guided flow (dry-run → resolve/create your profile → confirm → install → verify).

`--profile` picks `config/profiles/.md` to import into your generated `~/.claude/CLAUDE.md` and `~/.codex/AGENTS.md`. No existing profile and no `--profile`? It tries `gh api user --jq .login`; if that doesn't match an existing profile either, it copies `config/pro