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/seabbs/skills/show-diffnpx skills add seabbs/skills --skill show-diffgit clone --depth 1 https://github.com/seabbs/skillsWhat 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.00052 | $0.00480 |
| Opus 5 | $0.00026 | $0.00240 |
| Sonnet 5 | $0.00010 | $0.00096 |
| Haiku 4.5 | $0.00005 | $0.00048 |
Grade A, and why
show-diff 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 2d 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.
What it actually says
Show Diff
Open a new tmux pane that displays current changes via diffview.nvim,
so the user can review in a side-by-side viewer instead of scrolling
terminal output.
When to use
- After making more than a handful of edits, surface them for review
- User asks to see the diff, open a diff viewer, or review the changes
- Before asking the user to approve committing a larger change
Skip when edits are tiny, when not inside tmux, or when the user has already reviewed the changes in this turn.
How to run
bash ~/code/seabbs/dotfiles/scripts/show-diff.sh $ARGUMENTS
The script opens a right-hand split running nvim +DiffviewOpen <range>
rooted at the repo top-level.
Choosing the rev-range
Shortcuts the script understands:
| Argument | Expands to | Use when… |
|---|---|---|
| (none) | working tree vs HEAD | changes are uncommitted |
last |
HEAD~1..HEAD |
reviewing just the last commit |
last N or N |
HEAD~N..HEAD |
reviewing the last N commits |
pr |
origin/<base>...HEAD (base from gh pr view) |
on a branch with an open PR |
| any other value | passed through verbatim | explicit rev range, e.g. main...HEAD |
If the agent has both committed and uncommitted work on a feature
branch with an open PR, pr is the fastest choice.
Requirements
- Running inside tmux (script errors out otherwise)
- Inside a git repository
diffview.nvimavailable in neovim (already configured in the user's dotfiles)
After opening
Tell the user the pane is up and what range it shows. Do not try to drive the nvim instance from the agent side.
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.
- 2d ago First seen · 57 lines · 52 tokens per session scan A c7811d8c4948
show-diff is a skill published in the GitHub repository seabbs/skills (5 stars, last pushed 7d ago), licensed MIT. It adds 52 tokens to every session and 480 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-31.
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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.