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/zebbern/termstack/patch-diff-analyzernpx 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.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.1 | $0.00041 | $0.02159 |
| Opus 5 | $0.00020 | $0.01079 |
| Sonnet 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 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.
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.
- 2d 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 (5 stars, last pushed 4mo 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. 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
auto-issue-fixer
Issue 全生命周期管理——从创建到归档。当用户描述技术问题、提 bug、"帮我记录"、 "修一下 X issue"、"验证一下"、"归档 issue"时立即触发。单入口自动分发， 替代旧 issue-create/fix-issue/issue-verify/issue-archive 四个技能。 即使用户没有用"issue"这个词，只要在描述值得追踪的技术问题就应触发。.
codebase-index
代码库速查索引库 —— docs/code-index/ 下每个 crate 一个速查表文件，把「我想做什么」映射到具体文件、入口函数与一句话关键逻辑。当用户想定位或修改某个行为（"怎么改 compact 的触发阈值"、"keepgoing 判定在哪"、"加个 deferred 工具改哪里"、"事件链路怎么走"）、想快速了解某个模块的结构、或要求重建/更新代码索引时使用。用户没提"索引"二字但任务是找代码位置、改某个逻辑、理清调用链时，也应先查索引，而不是直接全库搜索。.
debugging
用科学方法定位 bug 的根因，而不是凭直觉乱改碰运气。核心：调试是观察 → 假设 → 设计实验验证 → 缩小范围 → 定位根因的循环，每一步都有依据。改到"不报错"不算修好——那可能只是把症状盖住了，根因还在。.
error-handling
设计或改进错误处理与日志时。.
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
交付前需验证完成，或修 bug 需修病因不修症状时。.