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/rlajous/claude-code-commands/change-briefnpx skills add rlajous/claude-code-commands --skill change-briefgit clone --depth 1 https://github.com/rlajous/claude-code-commandsWrote 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/rlajous/claude-code-commands/change-brief)<a href="https://agentmods.dev/skills/rlajous/claude-code-commands/change-brief"><img src="https://agentmods.dev/badge/skills/rlajous/claude-code-commands/change-brief.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.00118 | $0.02752 |
| Opus 5 | $0.00059 | $0.01376 |
| Sonnet 5 | $0.00024 | $0.00550 |
| Haiku 4.5 | $0.00012 | $0.00275 |
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 6d 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 — 216 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cross-runtime: follow runtime compatibility for invocation, delegation, configuration precedence, state paths, and permissions.
Produce a self-contained HTML decision brief per PR that a human can understand in less than 10 minutes. Explain what changed, why it matters, the business rules, how the flow works, what evidence proves it, and the relevant risks. Adapt the evidence to the change: diagrams for flows, screenshots for rendered UI/mobile work, and cURL request/response pairs for HTTP APIs. Never post a comment, review, or commit. Follow each step in order.
Arguments
$ARGUMENTS
Parse: a GitHub PR URL (/pull/N) → that PR number · a bare integer → that PR · empty → resolve the
PR open for the current branch (gh pr view --json number,... with no argument). If none of these
resolve to a PR, ask through the host's user-input mechanism which PR to use.
Step 1 — Resolve the change
gh pr view <pr> --json number,title,url,body,headRefName,baseRefName,baseRefOid,headRefOid,files
gh pr diff <pr>
- Pull each linked issue referenced in the PR body (
Fixes #NN,Closes #NN, etc.):gh issue view <NN> --json title,body. ghmissing or unauthenticated → tell the user and stop.- PR not found → say so and stop.
Classify the PR into one or more evidence kinds from changed paths and hunks:
- UI/web/mobile — rendered components, screens, styling, navigation, or interaction.
- HTTP API — routes, controllers, request/response schemas, OpenAPI, or HTTP integration tests.
- Business logic/data — rules, permissions, state transitions, calculations, persistence, jobs.
- Workflow/infrastructure — build, deployment, configuration, scripts, or developer tooling.
- Documentation-only — prose or examples without runtime behavior changes.
Read the evidence playbook after classification. Apply the common rules plus only the sections matching the detected kinds.
What ships with it
2 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.
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.
- 6d ago First seen · 216 lines · 118 tokens per session scan A 14593aae43d9
change-brief is a skill published in the GitHub repository rlajous/claude-code-commands (30 stars, last pushed 7d ago), licensed MIT. It adds 118 tokens to every session and 2,752 once invoked, about $0.0006 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…