A guided setup tool for cc-loadout, a command-line utility that chooses which Claude Code plugins are active in each code repository.

It helps inspect installed plugins, create repository-specific profiles, and activate the right plugins for each repository.

It avoids manually editing configuration files and helps ensure the selected plugin setup is actually applied.

init — Skill for Claude Code and Codex by XBlueSky: A guided setup tool for cc-loadout, a command-line utility…

Install

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.

agentmods

npx agentmods add skills/xbluesky/cc-loadout/init

Any agent

npx skills add XBlueSky/cc-loadout --skill init

Clone the repo

git clone --depth 1 https://github.com/XBlueSky/cc-loadout

Made for: Claude Code, Codex.

Or install cc-loadout, the plugin that ships this one along with the rest of its 4 skills, 2 hooks.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/xbluesky/cc-loadout/init.svg)](https://agentmods.dev/skills/xbluesky/cc-loadout/init)

Your own site

<a href="https://agentmods.dev/skills/xbluesky/cc-loadout/init"><img src="https://agentmods.dev/badge/skills/xbluesky/cc-loadout/init.svg" alt="Measured on agentmods" height="20"></a>

Per session 128 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,384 The whole file, excluding the scripts and references it only reads on demand.

Security scan B 1 finding. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What 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.00128	$0.01384
Opus 5	$0.00064	$0.00692
Sonnet 5	$0.00026	$0.00277
Haiku 4.5	$0.00013	$0.00138

Measured 3d ago against content hash 24598586ce3b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade B, and why

init 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 3d 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.

**global** enabled set in `~/.claude/settings.json` (universal stays on; every other

skills/init/SKILL.md · 108 lines

How it starts

The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Guided cc-loadout profile creation

You help the user build and activate ~/.claude/profiles/profiles.json for cc-loadout — the config that decides which Claude Code plugins load in which repos. You drive the cc-loadout CLI; you do not hand-write the JSON or touch settings.json yourself — the CLI validates and writes everything.

The end state (the "loadout" model): universal plugins stay enabled globally, every other managed plugin is turned off globally, and each repo re-enables just the plugins of the profiles it matches. That takes two CLI calls — profile init --assign (writes the config + adjusts the global set) and profile apply --all (enables per repo). Do both, or the change does not take effect.

Prerequisite

The cc-loadout CLI must be installed (cc-loadout --version). If it's missing, that's normally the SessionStart hook not having run yet or having failed — have the user start a fresh session first; install.sh (see the cc-loadout README) is the fix only for someone using the CLI without the plugin.

Steps

Inspect. Find out where the user keeps their git repos; ask for an absolute path if you don't already know it (cc-loadout does NOT expand ~ — use a full path). Then:
```
cc-loadout profile inventory --json --root <that path>
```
(Drop --root to use their existing scan_roots.) You get back { "schema_version": 1, "plugins": [...], "repos": [...], "suggested_profiles": [...] }. Ignore schema_version and any unknown key. Read plugins[].key, repos, and suggested_profiles[] (each suggested profile has a name and the detect markers found in that cluster of repos).
Interview. Using the inventory, decide the assignment with the user:
- Which installed plugins are universal (loaded in every repo)? Good universal picks never mis-fire anywhere (e.g. search / code-review tools).
- For each entry in suggested_profiles, which of the remaining plugins should it add? Confirm or skip each suggestion. (Profile names come from suggested_profiles[].name — you cannot invent new profile names here; the detect rules are derived from the scan.)

Read the full file on GitHub · 108 lines

Changes

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.

3d ago First seen · 108 lines · 128 tokens per session scan B 24598586ce3b

Subscribe to this mod's changes

init is a skill published in the GitHub repository XBlueSky/cc-loadout (2 stars, last pushed 6d ago), licensed MIT. It adds 128 tokens to every session and 1,384 once invoked, about $0.0006 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-31.

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

init