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 skills add melodic-software/claude-code-plugins --skill realign-file-namesgit clone --depth 1 https://github.com/melodic-software/claude-code-pluginsWrote 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/realign-file-names)<a href="https://agentmods.dev/skills/melodic-software/claude-code-plugins/realign-file-names"><img src="https://agentmods.dev/badge/skills/melodic-software/claude-code-plugins/realign-file-names/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/realign-file-names"><img src="https://agentmods.dev/badge/skills/melodic-software/claude-code-plugins/realign-file-names.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.00114 | $0.02072 |
| Opus 5.5 | $0.00046 | $0.00829 |
| Sonnet 5.5 | $0.00023 | $0.00414 |
| Haiku 4.5 | $0.00011 | $0.00207 |
Grade A, and why
realign-file-names 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 10d 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 — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository context. Gather first
Collect these with individual Bash calls, one command per call, never combined into a single invocation:
- Current branch,
git branch --show-current - Working tree status (empty = clean),
git status --porcelain | head -20 - Repository root,
git rev-parse --show-toplevel
The pipe is the bound and belongs in the command. A read-time cap bounds nothing: the Bash tool returns the command's complete output into context before there is anything to decide about.
Treat a failure as an unknown value and carry on.
Purpose
/docs-naming:audit-file-names decided what should be renamed and what each
citation of it may become. This skill is the hand that does it, and the gate
that keeps a human in front of every one.
A rename is not one edit. It is a tracked move plus a rewrite of every reference the tier rules allow, across files nobody opened, with a generated record and a frozen changelog somewhere in the set. That is exactly the shape of change an operator approves in bulk and regrets in review. So the unit here is one file, and the acceptance is one file's worth.
Read these before applying anything
| Read | For |
|---|---|
context/apply-recipe.md |
the present-apply-sweep-verify loop, and what a decline offers |
../../context/file-name-findings.md |
where the plan lives, the record's fields, its status arc, and why applying resumes |
../audit-file-names/context/tiers.md |
the form table to print before each acceptance |
One acceptance is one finding
Each explicit FN-xxxxxxxx in the argument is one acceptance. Nothing else is.
Refuse out loud, then re-present the current finding, when the operator
offers a range (FN-a through FN-d), a glob, a count (the first five), all,
everything, the rest, yes to all, or a bare go ahead standing in for the
set. Say what was refused and why: a blanket yes is one decision standing in for
many, and the rename this skill is about to make is the one the operator has not
read yet.
What ships with it
4 files 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.
- 10d ago Changed · +1 lines a0b217b550b2
- 14d ago Changed · -3 lines · -1 tokens per session 5fb5193fdcf5
- 17d ago Changed · -28 tokens per session 610e75a33233
- 1mo ago First seen · 164 lines · 143 tokens per session scan A 42a35ee920fc
realign-file-names is a skill published in the GitHub repository melodic-software/claude-code-plugins (25 stars, last pushed today), licensed MIT. It adds 114 tokens to every session and 2,072 once invoked, about $0.0005 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-13.
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.
auto-claude
Autonomous multi-agent coding with git worktree isolation, QA validation, and memory. Use for complex features requiring autonomous implementation.
changelog-summarizing
Use this skill when the user asks to summarize, recap, or post about repository changes in the Shopware AI Coding Tools marketplace since a given date — phrases like "write a changelog post for Discord", "recap this week's commits for Slack", "summarize what shipped since 2026-04-01", "draft a release announcement".…
find-shortest-path
For pathfinding and search: shortest path, maze solving, game AI, route planning, graph traversal, BFS/DFS, Dijkstra, A problems.
pass-function-as-arg
For generic algorithms: strategy pattern, callbacks, configurable behavior. Pass functions as parameters to customize algorithm behavior.