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/releasenpx skills add XBlueSky/cc-loadout --skill releasegit 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/release)<a href="https://agentmods.dev/skills/xbluesky/cc-loadout/release"><img src="https://agentmods.dev/badge/skills/xbluesky/cc-loadout/release.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.00090 | $0.00470 |
| Opus 5 | $0.00045 | $0.00235 |
| Sonnet 5 | $0.00018 | $0.00094 |
| Haiku 4.5 | $0.00009 | $0.00047 |
Grade A, and why
release 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.
What it actually says
Release an on-demand plugin
Prerequisite
The cc-loadout CLI must be installed (cc-loadout --version). If it is
missing, tell the user to install it and stop.
Steps
-
Resolve which plugin. If the user named one, use it directly. If not, list current holdings:
cc-loadout profile on-demand list --jsonand ask which
key(among those withlive_holders > 0) to release. -
Release it:
cc-loadout profile on-demand release <key>This releases only the CURRENT session's hold — if another session still holds the same plugin, it stays enabled for them (this is by design; holds are shared, not exclusive).
-
If the user is trying to clear a stuck hold from a crashed session (they mention a plugin that's still on despite no session using it, or ask to "force" release), confirm with them first — this reverts it regardless of any other session that might still hold it — then run:
cc-loadout profile on-demand release <key> --force
Boundaries
- Don't
--forcewithout confirmation. It reverts a hold regardless of other sessions still using it — always confirm with the user first (Step 3), never fire it just because a plugin "looks" stuck. - Don't release plugins the user isn't done with. Only release keys the
user names or confirms from the
live_holders > 0list — not every on-demand plugin the repo has ever acquired.
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 · 52 lines · 90 tokens per session scan A b331bd4f76ad
release is a skill published in the GitHub repository XBlueSky/cc-loadout (2 stars, last pushed yesterday), licensed MIT. It adds 90 tokens to every session and 470 once invoked, about $0.0005 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…