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 AutumnsGrove/ClaudeSkills --skill git-advancedgit clone --depth 1 https://github.com/AutumnsGrove/ClaudeSkillsWrote 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/autumnsgrove/claudeskills/git-advanced)<a href="https://agentmods.dev/skills/autumnsgrove/claudeskills/git-advanced"><img src="https://agentmods.dev/badge/skills/autumnsgrove/claudeskills/git-advanced/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/autumnsgrove/claudeskills/git-advanced"><img src="https://agentmods.dev/badge/skills/autumnsgrove/claudeskills/git-advanced.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.00101 | $0.02781 |
| Opus 5 | $0.00051 | $0.01391 |
| Sonnet 5 | $0.00020 | $0.00556 |
| Haiku 4.5 | $0.00010 | $0.00278 |
Grade A, and why
git-advanced 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 9d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
What ships with it
9 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.
- examples/branch_strategies.md 14 KB
- examples/conflict_resolution.md 12 KB
- examples/interactive_rebase.md 8.0 KB
- README.md 2.1 KB
- references/best-practices.md 9.1 KB
- references/branch-management.md 4.2 KB
- references/reflog-recovery.md 7.0 KB
- references/troubleshooting.md 11 KB
- scripts/git_helper.sh 12 KB runs code
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.
- 9d ago First seen · 498 lines · 101 tokens per session scan A fd4841a09657
git-advanced is a skill published in the GitHub repository AutumnsGrove/ClaudeSkills (30 stars, last pushed 10mo ago), with no licence file. It adds 101 tokens to every session and 2,781 once invoked, about $0.0005 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-08-30.
Other skills, from other repositories
branch-and-worktree-workflow
Isolates feature work in its own branch or worktree and integrates it cleanly when done. Use this when starting work that should not disturb the current workspace, when several efforts must proceed in parallel on one repository, or when implementation is finished and the change needs merging, rebasing, or splitting…
rudder-import-and-evolve
Imports existing RudderStack workspace resources into YAML files for git-based management. Use when importing existing RudderStack resources to CLI management and evolving them safely.
pdlc-ship
A software release workflow that runs tests, updates the version and change log, creates a Git tag, and starts CI/CD, the automated build and deployment process.
pdlc-changelog
A changelog updater that reads recent Git commits and records user-facing changes in a service or application’s CHANGELOG.md. A changelog is a history of additions, fixes, and other notable changes.
releasing
Use when releasing a bundle-plugin, bumping versions, fixing version drift across manifests, setting up version sync infrastructure, updating CHANGELOG, publishing to marketplaces, or checking release readiness.
pr-deslop
Use when cleaning AI slop, verbose commit messages, brittle references, or low-value changes from a branch before review.