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/melodic-software/claude-code-plugins/realignnpx skills add melodic-software/claude-code-plugins --skill realigngit 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)<a href="https://agentmods.dev/skills/melodic-software/claude-code-plugins/realign"><img src="https://agentmods.dev/badge/skills/melodic-software/claude-code-plugins/realign.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 | $0.00193 | $0.02396 |
| Opus 5 | $0.00097 | $0.01198 |
| Sonnet 5 | $0.00039 | $0.00479 |
| Haiku 4.5 | $0.00019 | $0.00240 |
Grade A, and why
realign 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 yesterday.
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 — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pre-computed context
!"${CLAUDE_PLUGIN_ROOT}/scripts/precompute.sh" realign 2>/dev/null || echo "- Orientation unavailable"
Purpose
Execute what the audit found, one finding at a time, with the operator deciding each one. This is the only mutating surface in this plugin, and the per-item gate below is the entire reason it is safe to point at a repository nobody has reviewed.
What makes these edits unusual is their target: every file this skill touches is a file that steers the agent's own behavior. A bad code edit fails a test. A bad instruction edit quietly changes what the agent does in every future session, and nothing goes red.
Read these before executing anything
Not restated here. A paraphrase inside a proposal is a drift seed.
| Read | For |
|---|---|
../../context/findings-artifact.md |
The artifact's location, fields, status vocabulary, merge rules |
../../context/routing-rubric.md |
The hard-deny classes and what each destination means |
../../context/verified-mechanics.md |
Why the shim is mandatory and why the index exists |
context/apply-recipes.md |
The exact edit sequence per destination, and the verification each one owes |
The per-item gate
Nothing mutates without an explicit acceptance of that finding, from the operator, at the moment it is presented. Say so in the run's opening line, then hold it literally.
- One finding, one acceptance. Accepting IP-003 authorizes IP-003 and nothing else, not its neighbours, not the rest of its file, not the obvious next one.
- Blanket approval is not the gate. "Approve everything", "do whatever the audit says", and a standing authorization from earlier in the session are all declined, out loud, with an offer to walk the findings one at a time. This is not pedantry: the whole value of the gate is that a human looked at each destination, and a blanket yes means nobody did.
- Present before asking. The source and its line range, the destination, the exact
paths:glob with its validated match count, what leaves the always-loaded budget, and the cost: subagent invisibility, and post-compaction behavior for that destination. - A decline is recorded, not argued. Write
declinedinto the artifact and move on. A declined finding is not re-proposed by a later audit.
What ships with it
2 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.
- yesterday First seen · 171 lines · 193 tokens per session scan A cdb9ca569ba7
realign is a skill published in the GitHub repository melodic-software/claude-code-plugins (14 stars, last pushed yesterday), licensed MIT. It adds 193 tokens to every session and 2,396 once invoked, about $0.0010 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-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…
kanban-dev-lane
Use when a Hermes Kanban worker wants to run an autonomous implementation delegation lane with a 3-tier fallback chain across claudy -> codex (--yolo) -> agyd (agy --dangerously-skip-permissions) -> Hermes direct on quota exhaustion.
survey
プロジェクト文脈を把握し .claude/context.md を作成する．新しいプロジェクトを始めるときに使う．context.md が既にある場合は /groundwork:theory を使う．.
implementation-spec
Master orchestrator that generates all implementation specs (PRD, Architecture, UX, Implementation, Test, Release) from product plan. Use when generating complete specification package.
monorepo
Monorepo management (Nx, Turborepo, pnpm workspaces) — task orchestration, caching, code sharing. Use when setting up monorepo, optimizing builds, or managing multi-package projects.
work-summary
Generates a project dashboard from MCP work items. Default is a lean, attention-first view: what's in flight, what's blocked, what to do next, what's queued. Use when the user says: project status, what's active, show me the dashboard, work summary, what should I work on, project health, what's blocked, where did I…