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 zebbern/termstack --skill patch-diff-analyzergit clone --depth 1 https://github.com/zebbern/termstackWrote 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/zebbern/termstack/patch-diff-analyzer)<a href="https://agentmods.dev/skills/zebbern/termstack/patch-diff-analyzer"><img src="https://agentmods.dev/badge/skills/zebbern/termstack/patch-diff-analyzer/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/zebbern/termstack/patch-diff-analyzer"><img src="https://agentmods.dev/badge/skills/zebbern/termstack/patch-diff-analyzer.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.00041 | $0.02159 |
| Opus 5.5 | $0.00016 | $0.00864 |
| Sonnet 5.5 | $0.00008 | $0.00432 |
| Haiku 4.5 | $0.00004 | $0.00216 |
Grade B, and why
patch-diff-analyzer scanned grade B 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 1mo 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 deletemediumDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf <workspace>/decompiled/* Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
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
13 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/example-workflow.md 6.6 KB
- examples/example-workflow.mdZone.Identifier 25 B
- README.md 114 B
- README.mdZone.Identifier 25 B
- scripts/analyze-diff.sh 2.7 KB runs code
- scripts/analyze-diff.shZone.Identifier 25 B
- scripts/decompile-dll.sh 2.4 KB runs code
- scripts/decompile-dll.shZone.Identifier 25 B
- scripts/decompile-jar.sh 2.1 KB runs code
- scripts/decompile-jar.shZone.Identifier 25 B
- scripts/setup-workspace.sh 1.2 KB runs code
- scripts/setup-workspace.shZone.Identifier 25 B
- SKILL.mdZone.Identifier 25 B
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.
- 1mo ago First seen · 323 lines · 41 tokens per session scan B bfe43e6acc16
patch-diff-analyzer is a skill published in the GitHub repository zebbern/termstack (4 stars, last pushed 6mo ago), with no licence file. It adds 41 tokens to every session and 2,159 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
debugging
A methodical way to find the underlying cause of software bugs by observing what happens, forming hypotheses, and testing them. It separates finding the cause from applying and checking the fix.
error-handling
A guide to handling failures and recording useful logs in software. It explains when to pass an error upward, handle it locally, or retry it.
health
Code Quality Dashboard. Runs the project's type-checker, linter, test runner, and dead-code detector, scores each category 0-10, and presents a dashboard with trends. Use when asked for a "health check", "code quality report", or "quality dashboard".
verify-and-fix
A verification-and-repair workflow for checking finished code with tests, type checks, or a real run of the target scenario. It treats verification as evidence that the work is complete.
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
debug
Reproduce, minimize, localize, identify root cause, and distinguish diagnosis from an authorized fix. Prefer root-cause over symptom patches.