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/chen3feng/agent-skills/git-rev-parse-multi-ref-shortnpx skills add chen3feng/agent-skills --skill git-rev-parse-multi-ref-shortgit clone --depth 1 https://github.com/chen3feng/agent-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/chen3feng/agent-skills/git-rev-parse-multi-ref-short)<a href="https://agentmods.dev/skills/chen3feng/agent-skills/git-rev-parse-multi-ref-short"><img src="https://agentmods.dev/badge/skills/chen3feng/agent-skills/git-rev-parse-multi-ref-short.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.00030 | $0.01056 |
| Opus 5 | $0.00015 | $0.00528 |
| Sonnet 5 | $0.00006 | $0.00211 |
| Haiku 4.5 | $0.00003 | $0.00106 |
Grade A, and why
git-rev-parse-multi-ref-short 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 4d 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
git rev-parse --short rejects multiple refs
When to use
You want to verify that several branches / tags / commits all point
to the same object (e.g. right after cutting a release branch and
tag from the same master HEAD) and you reach for the one-liner
git rev-parse --short v2.0.1 2.x v3 master
…only to get fatal: Needed a single revision. Same if you drop the
shortening length (--short=7 …).
Problem
git rev-parse --short (or --short=<n>) is documented as an
abbreviation flag: it takes exactly one object and prints its
shortened hash. Passing more than one ref flips git into a different
code path that aborts with:
fatal: Needed a single revision
exit status 128. This is independent of whether the refs resolve to
the same commit — git rejects the invocation before resolving.
Without --short, the very same argument list works fine:
$ git rev-parse v2.0.1 2.x v3 master
84f89b4e30ebbf44caef67103b546f4990e94c83
84f89b4e30ebbf44caef67103b546f4990e94c83
84f89b4e30ebbf44caef67103b546f4990e94c83
84f89b4e30ebbf44caef67103b546f4990e94c83
The trap is that the error message (Needed a single revision) reads
like "you gave me zero" or "I couldn't parse one", not "you gave
me too many combined with --short". Agents often respond by
tweaking the refs rather than dropping the flag.
Solution
Pick the shape that matches your intent:
| Goal | Recipe |
|---|---|
| Multiple refs, full SHA | git rev-parse ref1 ref2 ref3 |
| Multiple refs, short SHA, one line | for r in ref1 ref2 ref3; do git rev-parse --short "$r"; done |
| Multiple refs, short SHA, labelled | for r in ref1 ref2 ref3; do echo "$r -> $(git rev-parse --short "$r")"; done |
| Single ref, short SHA | git rev-parse --short ref1 (the canonical use) |
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.
- 4d ago First seen · 106 lines · 30 tokens per session scan A 09feeb42b123
git-rev-parse-multi-ref-short is a skill published in the GitHub repository chen3feng/agent-skills (5 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 30 tokens to every session and 1,056 once invoked, about $0.0002 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…