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/xbluesky/cc-loadout/acquirenpx skills add XBlueSky/cc-loadout --skill acquiregit clone --depth 1 https://github.com/XBlueSky/cc-loadoutWrote 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.
[](https://agentmods.dev/skills/xbluesky/cc-loadout/acquire)<a href="https://agentmods.dev/skills/xbluesky/cc-loadout/acquire"><img src="https://agentmods.dev/badge/skills/xbluesky/cc-loadout/acquire.svg" alt="Measured on agentmods" height="20"></a>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.1 | $0.00122 | $0.00782 |
| Opus 5 | $0.00061 | $0.00391 |
| Sonnet 5 | $0.00024 | $0.00156 |
| Haiku 4.5 | $0.00012 | $0.00078 |
Grade A, and why
acquire scanned grade A with 0 findings 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 5d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Acquire an on-demand plugin for this session
You enable a Profiles.on_demand plugin in the current repo, scoped to this
session, via the cc-loadout CLI. You do not edit .claude/settings.local.json
or the on-demand state file yourself — the CLI does both.
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 is the fix
only for someone using the CLI without the plugin.
Steps
-
Resolve which plugin. If the user named one (e.g.
/cc-loadout:acquire pixijs-skills), match it against the on_demand list:cc-loadout profile on-demand list --jsonFuzzy-match the given name against the returned
keys (e.g.pixijs-skillsmatchingpixijs-skills@some-marketplace). If there's no match, show the full list and ask which one they meant — do not guess silently.If the user gave no name, run the same
list --jsoncommand, present everykey(and itslive_holderscount if non-zero) to the user, and ask which one to acquire. -
Acquire it:
cc-loadout profile on-demand acquire <key>If this fails with a
CC_LOADOUT_SESSION_ID not seterror, tell the user the cc-loadout SessionStart hook hasn't run in this session yet — starting a fresh session is the first thing to try — and stop. -
Tell the user to reload. The plugin is now enabled in
.claude/settings.local.json, but Claude Code doesn't pick up newly enabled plugin components until you run:/reload-pluginsTell the user to run it now themselves — you cannot invoke a slash command on their behalf.
-
Remind them it's session-scoped. It will revert automatically when this session ends (via the cc-loadout SessionEnd hook). If they want to release it early, point them at
/cc-loadout:release.
Guardrails
- Let the CLI own state. Do not edit
.claude/settings.local.jsonor the on-demand state file directly yourself —cc-loadout profile on-demand acquiredoes both. - Only
on_demandplugins are acquirable. A plugin not returned byprofile on-demand listcannot be acquired this way — it needs to be added toProfiles.on_demandfirst (via/cc-loadout:init's Assign flow). - Never invoke
/reload-pluginson the user's behalf. Tell them to run it themselves; no hook can fire a slash command for them.
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.
- 5d ago First seen · 72 lines · 122 tokens per session scan A 45aa0a5f6920
acquire is a skill published in the GitHub repository XBlueSky/cc-loadout (2 stars, last pushed yesterday), licensed MIT. It adds 122 tokens to every session and 782 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
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…
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…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…