Borrowing it
Nothing to install: this file belongs to VasiHemanth/tokentelemetry. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/VasiHemanth/tokentelemetry/main/.claude/skills/change-brief/SKILL.mdgit clone --depth 1 https://github.com/VasiHemanth/tokentelemetryWrote 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/vasihemanth/tokentelemetry/change-brief)<a href="https://agentmods.dev/skills/vasihemanth/tokentelemetry/change-brief"><img src="https://agentmods.dev/badge/skills/vasihemanth/tokentelemetry/change-brief/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/vasihemanth/tokentelemetry/change-brief"><img src="https://agentmods.dev/badge/skills/vasihemanth/tokentelemetry/change-brief.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.00000 | $0.03612 |
| Opus 5.5 | $0.00000 | $0.01445 |
| Sonnet 5.5 | $0.00000 | $0.00722 |
| Haiku 4.5 | $0.00000 | $0.00361 |
Grade A, and why
change-brief 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 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.
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 — 271 lines — stays where its author put it; the contents beside it link to each section on GitHub.
change-brief — explain a change that already exists
/issue-brief explains something not yet built, to decide whether to build
it. This skill explains something already written, so the reader
understands what it does and whether to merge or trust it.
The reader did not write this code. Often nobody they can ask wrote it — it may be an outside contributor's PR, or something Claude produced in a session they have since forgotten. Assume no memory of the change and no file layout in their head.
1. Resolve the target
| They said | Fetch with |
|---|---|
| PR number or URL | gh pr view <n> --json number,title,author,body,files,additions,deletions,mergeable,mergeStateStatus,commits |
| "what is 331" (bare number) | Try gh pr view <n> first; fall back to gh issue view <n> |
| commit SHA | git show --stat <sha> |
| "these changes" / "what did you change" | git status --short and git diff (plus git diff --staged) |
| merged issue | gh issue view <n>, then find the PR that closed it |
Get the real diff, not the description. A PR opened weeks ago is measured against today's base:
git fetch origin main pull/<n>/head:pr<n>
git diff origin/main...pr<n> --stat
A git diff main... against a stale local main reports hundreds of unrelated
files. If the stat looks absurdly large for the PR's description, that is the
cause — fetch origin/main and re-diff before believing it.
2. Establish authorship — this is not optional
The user asked for this explicitly: never explain a change without saying who wrote it. They need to know whether they are reading their own past decision, a contributor's proposal, or Claude's output from a session they don't recall.
It lands in position 2, immediately after the opening model (§3 step 1) and before any mechanism. That is a deliberate change: it used to go first, and a brief that opened with a username, three PR numbers and a timestamp got "explain it clearly, I still didn't understand" in reply. A name means nothing until the reader knows what the thing does. Two lines, still never skipped.
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 · 271 lines · 0 tokens per session scan A d805ebb432c6
change-brief is a skill published in the GitHub repository VasiHemanth/tokentelemetry (386 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,612 tokens. 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-09-12.
Other skills, from other repositories
feature-publish
Commit the feature, write the PR body, publish in the selected mode, and drive the PR.
lean-review
CocoLean diff-scoped over-engineering audit — scans uncommitted git diff and applies five classification tags (delete/stdlib/native/yagni/shrink) to identify unnecessary surface area before commit.
flag-cleanup
Weekly reusable-session feature-flag cleanup for {{targetrepo}}. Inventories every feature flag, classifies each as fully rolled out, long dead, partial rollout, or active experiment, removes the flag and the dead branch it guards on an isolated branch when the suite is green, and opens a PR — never touching a flag…
github-commenting
How to post clean, rich, deduplicated GitHub PR review comments — suggestion blocks, multi-line anchors, markers, formatting rules. Load before posting or fixing any PR comment.
guardian
Gatekeeping Git/PR by classifying change essence and recommending granularity, naming, and strategy; the ship recipe also executes PR delivery (create, CI watch, merge, cleanup) with Ask First on merge. Use when PR preparation, commit strategy, or gated PR delivery is needed.
code-changes
Change the user's own program, on their machine or through GitHub. Use when a request needs a change to the user's code (instrument tracing, wire the SDK, fix the agent behind a failing scenario, add a run parameter to a connected agent, version a hardcoded prompt) and not when the platform alone can do it (create a…