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.
git clone --depth 1 https://github.com/pleaseai/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/commands/pleaseai/claude-code-plugins/reorder)<a href="https://agentmods.dev/commands/pleaseai/claude-code-plugins/reorder"><img src="https://agentmods.dev/badge/commands/pleaseai/claude-code-plugins/reorder/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/commands/pleaseai/claude-code-plugins/reorder"><img src="https://agentmods.dev/badge/commands/pleaseai/claude-code-plugins/reorder.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.00012 | $0.00331 |
| Opus 5 | $0.00006 | $0.00166 |
| Sonnet 5 | $0.00002 | $0.00066 |
| Haiku 4.5 | $0.00001 | $0.00033 |
Grade A, and why
reorder 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.
What it actually says
Reshuffle the order of branches in the current stack via an editor-based picker. User input: $ARGUMENTS.
How it works
gt reorder opens $EDITOR with the current branch and its ancestors (downstack), one branch per line. Rearrange the lines to set the new order. You can also delete lines (removes the branch from the stack) or add lines (must reference branches Graphite already knows about).
Steps
- Run
gt lsto show the user the stack today. - Ask which form they want:
gt reorder— just the downstack of the current branch.gt reorder --stack— the entire stack (trunk → tip).
- Run the command. Graphite will open the editor; if the session is non-interactive, suggest using
/graphite:move --onto <branch>to reposition one branch at a time instead. - On save, Graphite performs the restacks. Resolve any conflicts as usual:
gt add .→gt continue -a, orgt abort. - Run
gt lsto confirm.
When to prefer alternatives
- Moving a single branch to a new parent →
/graphite:movewith--onto <branch>. - Inserting a new branch mid-stack →
gt create --insert -am "..."(covered by/graphite:create).
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 · 27 lines · 12 tokens per session scan A 9b4fb41609f1
reorder is a command published in the GitHub repository pleaseai/claude-code-plugins (13 stars, last pushed yesterday), licensed MIT. It adds 12 tokens to every session and 331 once invoked, about $0.0001 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-07.
Other commands, from other repositories
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
handoff
Export a Waybill Bundle by default, or import one when requested.
pr
Handle the full workflow from current branch state to an open, CI-monitored pull request.