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 hxy91819/mason-skills --skill what-changedgit clone --depth 1 https://github.com/hxy91819/mason-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/hxy91819/mason-skills/what-changed)<a href="https://agentmods.dev/skills/hxy91819/mason-skills/what-changed"><img src="https://agentmods.dev/badge/skills/hxy91819/mason-skills/what-changed/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/hxy91819/mason-skills/what-changed"><img src="https://agentmods.dev/badge/skills/hxy91819/mason-skills/what-changed.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.00028 | $0.00514 |
| Opus 5 | $0.00014 | $0.00257 |
| Sonnet 5 | $0.00006 | $0.00103 |
| Haiku 4.5 | $0.00003 | $0.00051 |
Grade A, and why
what-changed 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 7d 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
What Changed
用户要听的是改动说明，不是代码走查。核心原则：讲决定，用按意图分类的精简清单呈现。
1. 先确定范围
按用户的问法选一个：
- 上一轮：本次会话最近一次完成的改动，凭会话记录回答，记不清的部分回去看当时的 diff。
- 当前 diff：工作区或当前分支上还没发布的改动，直接看
git diff（含暂存区）。 - 当前 PR/MR：整条分支相对目标分支的全部改动，看
git log和 PR/MR 的 diff。
范围含糊时选最近完成的那次改动，并在回答开头说明你选了哪个范围。不要只凭记忆复述大范围改动。
2. 用分类清单回答三个问题
- 这次改动要解决什么问题。
- 做了哪几个决定来解决问题。用 Markdown 勾选清单按意图归类；只展示有改动的分类。可用分类包括“功能与行为”“接口、数据与配置”“质量与维护”。每项是一项决定，写清改了什么和为什么，不按文件或代码行罗列。这是回答的主体。
- 用户现在能看到什么变化，什么保持不变。
3. 简单明了，字数要少
先给一句话结论，再给最必要的理由；细节、文件名、备选方案都等用户追问再说。分类通常不超过三个，每类一到两项；改动小就更短，一两句或一个清单项说完，不硬套结构。
宁可少说，让用户来问，不要一次说完。
4. 用平实语言
短句，常用词，一句话只说一个意思。文件名、命令、接口名只在用户需要定位时才提，放在句子的次要位置。
完成标准：不看代码的人能复述出“改了什么、为什么”；清单按意图分类、能快速扫读，且没有逐文件或逐行的罗列。
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.
- 7d ago Changed · -1 lines f7e8d2b88010
- 11d ago First seen · 38 lines · 28 tokens per session scan A 5ba314840938
what-changed is a skill published in the GitHub repository hxy91819/mason-skills (2 stars, last pushed today), licensed MIT. It adds 28 tokens to every session and 514 once invoked, about $0.0001 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
autoreview
Pre-commit/ship code review: Codex default; optional Claude or Pi.
omh-code-review
This is a Hermes-native code-review workflow skill.
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
code-reviewer
Code review specialist focused on patterns, bugs, security, and performance.
full-repo-review
Comprehensive four-wave review of all repo source files, producing a prioritized issue backlog.
agent-teams-simplify-and-harden
Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or…