Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/rlajous/claude-code-commands/setupnpx skills add rlajous/claude-code-commands --skill setupgit clone --depth 1 https://github.com/rlajous/claude-code-commandsWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00049 | $0.01322 |
| Opus 5 | $0.00024 | $0.00661 |
| Sonnet 5 | $0.00010 | $0.00264 |
| Haiku 4.5 | $0.00005 | $0.00132 |
Grade B, and why
setup scanned grade B with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- Codex: update the selected project `.codex/config.toml` or explicit user `~/.codex/config.toml` MCP tables without replacing unrelated settings. How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Set up Git Workflow
Follow runtime compatibility. Claude Code users invoke this as /setup; Codex users invoke it as $setup.
1. Resolve roots and runtime
Parse these options before resolving paths:
--host <claude|codex|both>selects exactly which project assets to synchronize. When omitted, detect the active host and ask only if the target remains ambiguous.--dry-runpreviews migration and installation without creating directories, files, or ledgers.--forceis explicit approval to replace customized selected-host files, but differences must still be shown first.- Reject unknown options and missing option values without writing.
Resolve {SKILL_DIR} to the absolute, physical directory containing this loaded SKILL.md.
Codex includes that path in its skill metadata; Claude Code can resolve the loaded skill path too.
Only when the host does not expose the path, use PLUGIN_ROOT, then CLAUDE_PLUGIN_ROOT, to locate
skills/setup/SKILL.md and verify that it exists. Never substitute an empty variable or silently
fall back to /scripts.
Derive {PACKAGE_ROOT} as the physical {SKILL_DIR}/../.. directory and require
{PACKAGE_ROOT}/.codex-plugin/plugin.json. Resolve the project root with
git rev-parse --show-toplevel, falling back to the current directory.
Detect the active host from available environment and configuration. If both Claude and Codex appear active and the requested target is unclear, ask which host or hosts to configure.
Never edit a user-global configuration unless the user explicitly selects global scope.
2. Migrate workflow configuration
Canonical configuration is <project>/.git-workflow/config.yaml.
- If only
.claude/config.yamlexists, explain that it is the legacy location and offer to copy it to the canonical path. - Create
.git-workflow/before copying. - Never delete or modify the legacy file automatically.
- If both files exist, use the canonical file. Show a diff when they differ and do not merge or overwrite without an explicit user decision.
- If neither exists, ask only for values that differ from the documented defaults, then write the canonical file from
templates/config.yaml.template.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 103 lines · 49 tokens per session scan B 2dd2a9ebbef8
setup is a skill published in the GitHub repository rlajous/claude-code-commands (30 stars, last pushed 3d ago), licensed MIT. It adds 49 tokens to every session and 1,322 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…