Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add melodic-software/claude-code-plugins/plugin install disciplineWrote 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/melodic-software/claude-code-plugins/use-your-skills)<a href="https://agentmods.dev/skills/melodic-software/claude-code-plugins/use-your-skills"><img src="https://agentmods.dev/badge/skills/melodic-software/claude-code-plugins/use-your-skills/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/melodic-software/claude-code-plugins/use-your-skills"><img src="https://agentmods.dev/badge/skills/melodic-software/claude-code-plugins/use-your-skills.svg" alt="Reviewed on agentmods" width="80" 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.00104 | $0.01748 |
| Opus 5.5 | $0.00042 | $0.00699 |
| Sonnet 5.5 | $0.00021 | $0.00350 |
| Haiku 4.5 | $0.00010 | $0.00175 |
Grade A, and why
use-your-skills 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Use your skills
A drift corrector for skill-use discipline: the skills are in context to be
used, not ignored. The shared method (re-anchor, audit the work in flight,
correct forward, report) lives in
${CLAUDE_PLUGIN_ROOT}/context/re-anchor-audit-correct.md.
Read it; this file adds only what is specific to discovering and invoking the
skills already available.
The discipline this re-anchors
A skill listing is loaded into context so the model knows what is available:
every model-invocable skill's name (always) and its description (subject to
the listing budget), with the full body loading only when the skill is invoked
(Skills docs, fetched 2026-08-10;
recheck when that page stops describing the listing as name-plus-description
with the body loaded on invocation, or when a release note changes what the
skill listing carries).
A manual-only skill never reaches the model's listing; which frontmatter
makes a skill manual-only, and which only hides it from the / menu while
leaving it model-visible:
Control who invokes a skill,
as of 2026-10-14; recheck when that section changes which flag removes a skill
from the model's listing. This corrector therefore audits only what the model
could actually have reached: a model-visible skill that sat in the listing
and went unused, its procedure reinvented or skipped instead of invoked. It
does not fault the model for not auto-firing a manual-only skill.
The discipline, at each of the three surfaces where skills apply:
- This conversation. Before doing multi-step or specialized work, scan the in-context listing for a skill that already owns it, and invoke that skill rather than improvising the procedure. Read a skill's description as a routing signal, not decoration.
- The current task. Map the task's shape to the skills that fit it, often more than one across a task's phases (research, plan, implement, review), and invoke each at its moment rather than carrying the whole task by hand.
- Delegated (subagent) work. Never assume a delegated subagent knows
which skills fit its task: name the relevant skills in the delegation
prompt. For a custom subagent that
should always carry a discipline, recommend its
skills:frontmatter, after checking the preload section below for which skills it can carry; a skill it cannot preload goes into the prompt directly. This is guidance, not a config change the skill performs.- Pointer: when deciding between naming a skill in the prompt and preloading it, fetch https://code.claude.com/docs/en/sub-agents#preload-skills-into-subagents live; for what a non-fork subagent's context holds at startup, fetch https://code.claude.com/docs/en/sub-agents#what-loads-at-startup live.
- As of: 2026-10-11
- Recheck trigger: either section changes which skills a subagent can preload or invoke, or what a non-fork subagent receives at startup.
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.
- 5d ago Changed · -8 lines · -2 tokens per session 2ab39af17d5b
- 7d ago Changed · -2 lines 70e1ac4701c7
- 17d ago Changed 5171549ac0b7
- 22d ago Changed · -39 tokens per session c26a1316f65b
- 1mo ago Changed · +3 lines 5ade1b63d3ba
- 1mo ago Changed · +1 tokens per session 4dd9286475f5
- 1mo ago Changed · +2 lines 9d3cd69df055
- 1mo ago Changed · -8 lines 66cee2d3e004
- 1mo ago First seen · 145 lines · 144 tokens per session scan A 3a34f32f40fd
use-your-skills is a skill published in the GitHub repository melodic-software/claude-code-plugins (26 stars, last pushed today), licensed MIT. It adds 104 tokens to every session and 1,748 once invoked, about $0.0004 per session on Opus 5.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-09-03.
Other skills, from other repositories
parallel-orchestrator
Manage parallel Claude Code workstreams using git worktrees. Use when: splitting large tasks across multiple workers, coordinating parallel development, monitoring worker progress, integrating completed work, analyzing work item documents (code reviews, issue lists). Triggers: parallel, orchestrator, worktrees…
parallel-worker
Execute focused implementation tasks in a parallel workflow. Use when: working on assigned files in a worktree, making checkpoint commits, signaling dependencies or blockers, completing orchestrator-assigned tasks. Triggers: worker, checkpoint, worktree, assigned scope, commit prefix, parallel task.
optimize-local-search
For NP-hard optimization: TSP, scheduling, assignment problems. Uses greedy construction + local improvement (2-opt, hill climbing).
solve-constraint-puzzle
For constraint satisfaction: Sudoku, scheduling, N-queens, logic puzzles, SAT-like problems, assignment problems. Uses propagate-then-search pattern.
test-with-examples
For example-driven development: test cases as specifications, input/output pairs, documentation through examples.
return-none-for-failure
For graceful failure: return None or False instead of exceptions, let caller decide how to handle failure.