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/arittr/spectacular/using-git-spicenpx skills add arittr/spectacular --skill using-git-spicegit clone --depth 1 https://github.com/arittr/spectacularWhat 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.00055 | $0.02252 |
| Opus 5 | $0.00028 | $0.01126 |
| Sonnet 5 | $0.00011 | $0.00450 |
| Haiku 4.5 | $0.00006 | $0.00225 |
Grade A, and why
using-git-spice 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 3d 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 — 278 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using git-spice
Overview
git-spice (gs) is a CLI tool for managing stacked Git branches and their Change Requests.
Core principle: git-spice tracks branch relationships (stacks) and automates rebasing/submitting dependent branches.
Key Concepts
Stack terminology:
- Stack: All branches connected to current branch (both upstack and downstack)
- Upstack: Branches built on top of current branch (children and descendants)
- Downstack: Branches below current branch down to trunk (parents and ancestors)
- Trunk: Main integration branch (typically
mainormaster)
Example stack:
┌── feature-c ← upstack from feature-b
├── feature-b ← upstack from feature-a, downstack from feature-c
├── feature-a ← downstack from feature-b
main (trunk)
When on feature-b:
- Upstack: feature-c
- Downstack: feature-a, main
- Stack: feature-a, feature-b, feature-c
Quick Reference
| Task | Command | Notes |
|---|---|---|
| Initialize repo | gs repo init |
Required once per repo. Sets trunk branch. |
| Create stacked branch | gs branch create <name> |
Creates branch on top of current. Use gs bc shorthand. |
| View stack | gs log short |
Shows current stack. Use gs ls or gs log long (gs ll) for details. |
| Submit stack as PRs | gs stack submit |
Submits entire stack. Use gs ss shorthand. |
| Submit upstack only | gs upstack submit |
Current branch + children. Use gs us s shorthand. |
| Submit downstack only | gs downstack submit |
Current branch + parents to trunk. Use gs ds s shorthand. |
| Rebase entire stack | gs repo restack |
Rebases all tracked branches on their bases. |
| Rebase current stack | gs stack restack |
Rebases current branch's stack. Use gs sr shorthand. |
| Rebase upstack | gs upstack restack |
Current branch + children. Use gs us r shorthand. |
| Move branch to new base | gs upstack onto <base> |
Moves current + upstack to new base. |
| Sync with remote | gs repo sync |
Pulls latest, deletes merged branches. |
| Track existing branch | gs branch track [branch] |
Adds branch to git-spice tracking. |
| Delete branch | gs branch delete [branch] |
Deletes branch, restacks children. Use gs bd shorthand. |
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.
- 3d ago First seen · 278 lines · 55 tokens per session scan A a1ee3f312ea1
using-git-spice is a skill published in the GitHub repository arittr/spectacular (20 stars, last pushed 7mo ago), licensed MIT. It adds 55 tokens to every session and 2,252 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…