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 Xakki/ai-agents-skills/plugin install ai-agents-skillsWrote 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/xakki/ai-agents-skills/git-move)<a href="https://agentmods.dev/skills/xakki/ai-agents-skills/git-move"><img src="https://agentmods.dev/badge/skills/xakki/ai-agents-skills/git-move/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/xakki/ai-agents-skills/git-move"><img src="https://agentmods.dev/badge/skills/xakki/ai-agents-skills/git-move.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.00088 | $0.00411 |
| Opus 5 | $0.00044 | $0.00205 |
| Sonnet 5 | $0.00018 | $0.00082 |
| Haiku 4.5 | $0.00009 | $0.00041 |
Grade C, and why
git-move scanned grade C with 1 finding 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 8d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- Untracked path, or not in a git repo → plain `mv` / `rm -rf` (fallback). What it actually says
git-move — file ops that respect git
When moving, renaming, or deleting a file/directory that might be tracked by
git, never use bare mv / rm — that drops git's rename/delete tracking and
leaves the index inconsistent. Use the helper:
ROOT="${AI_AGENTS_SKILLS_ROOT:-${CLAUDE_PLUGIN_ROOT:-${PLUGIN_ROOT:-${CURSOR_PLUGIN_ROOT:-}}}}"
"$ROOT"/skills/git-move/git-move.sh <src> <dst> # move / rename
"$ROOT"/skills/git-move/git-move.sh --rm <path> [path…] # delete
Behaviour:
- Tracked path inside a work tree →
git mv/git rm(history + index stay clean). - Untracked path, or not in a git repo → plain
mv/rm -rf(fallback). - Destination parent dirs are created automatically (
mkdir -p). - Staging only — it never commits. You commit separately when asked, following the git-flow core.
Examples:
"$ROOT"/skills/git-move/git-move.sh .claude/kanban/grooming/foo.md .claude/kanban/todo/foo.md
"$ROOT"/skills/git-move/git-move.sh --rm .claude/kanban/todo/old.md .claude/kanban/todo/dup.md
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.
- 8d ago First seen · 31 lines · 88 tokens per session scan C 2c94245f9bd3
git-move is a skill published in the GitHub repository Xakki/ai-agents-skills (6 stars, last pushed 18d ago), licensed MIT. It adds 88 tokens to every session and 411 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
taiyi-integration
A project workflow skill for closing a TaiyiForge change and recording it in a CHANGELOG.md file. It checks review results, tests, and the state of the working tree before archiving the change.
security-pipeline
Use when security verification is needed - pre-commit security checks, vulnerability scanning, STRIDE threat analysis. Integrates with /handoff-verify --security and /commit-push-pr. CWE Top 25 based.
docs-release-notes
Use when a change needs a user-visible release-note, changelog, or changeset entry — "add a release note", "add a changeset for this", "what goes in the changelog?", "write up what shipped", "note this for the next release" — or when finalizing a branch whose customer-visible features, bug fixes, or UI changes should…
docs-sync-internal
Use when code changes on the current branch need matching internal or developer documentation — "update our internal docs", "the architecture docs are stale after this change", "document what I just changed", "do the dev docs still match the code?" — or as a pre-push check that developer docs track the code. Narrower…
pr-description
Use when generating or updating a PR description for the current branch. Takes an optional issue number as argument.
retrospective-audit
Stage B of /prflow:retrospective-weekly: given a most-recent-first subset of one recurring pattern's occurrence-PR context bundles (bounded by auditbundlecap), re-derive the root cause and return one JSON object carrying a ranked findings array (one to three sub-patterns) — no edits, no worktree. Invoked as a subagent…