Borrowing it
Nothing to install: this file belongs to nick-pape/grackle. 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/nick-pape/grackle/main/.claude/skills/rush-change/SKILL.mdgit clone --depth 1 https://github.com/nick-pape/grackleWrote 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/nick-pape/grackle/rush-change)<a href="https://agentmods.dev/skills/nick-pape/grackle/rush-change"><img src="https://agentmods.dev/badge/skills/nick-pape/grackle/rush-change.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.00027 | $0.01028 |
| Opus 5 | $0.00014 | $0.00514 |
| Sonnet 5 | $0.00005 | $0.00206 |
| Haiku 4.5 | $0.00003 | $0.00103 |
Grade A, and why
rush-change 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.
How it starts
The opening of the file, as written. The whole thing — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rush Change — Smart Change File Generator
This skill generates a Rush change file for the current branch. It detects merge-commit false positives (where rush change --verify flags packages that have no real diff against main) and handles them automatically.
Important: How Rush Lockstep Versioning Works
All publishable packages use lockstep versioning — they share the same version number. Rush will always flag @grackle-ai/cli as the package needing a change file, regardless of which package you actually changed. This is because Rush picks one representative package from the lockstep group.
The change file is always created for @grackle-ai/cli, but the comment and bump type should describe ALL the changes in your PR across ALL packages. For example, if you changed packages/server/ and packages/mcp/, the change file is still for @grackle-ai/cli but the comment should describe the server and MCP changes.
Step 1: Check if Rush Requires a Change File
git fetch origin
node common/scripts/install-run-rush.js change --verify 2>&1
If this passes (exit 0), no change file is needed. Report success and stop.
Step 2: Determine Real vs False-Positive Changes
Rush says a change file is needed. Now determine whether publishable packages actually changed, or if this is a merge-commit false positive.
Get the net committed diff against main (explicit two-ref diff — compares branch tip to origin/main, ignoring merge commit artifacts and uncommitted changes):
git diff --name-only origin/main HEAD
Check if any of the changed files fall within a publishable package directory:
packages/cli/packages/common/packages/powerline/packages/server/packages/adapter-sdk/packages/mcp/
Case A: Real changes in publishable packages
If the diff touches publishable package directories, this is a real change that needs a proper change file.
- Examine the diff to determine the appropriate bump type:
patch— bug fixes, internal refactoring, dependency updates, test-only changesminor— new features, new APIs, backwards-compatible additions- Never use
major— CI blocks major bumps (pre-1.0) - Never use
nonefor real changes — all publishable packages ship together in lockstep, so any real change (even test-only) should bepatchorminor
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 First seen · 113 lines · 27 tokens per session scan A 8b9451cec425
rush-change is a skill published in the GitHub repository nick-pape/grackle (21 stars, last pushed 2mo ago), licensed MIT. It adds 27 tokens to every session and 1,028 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-30.
Other skills, from other repositories
source-control
Commit message format and release PR process. Use when ready to commit or push a release; use task-transitions for task close/review gates.
github-ops
GitHub repository operations, automation, and management. Issue triage, PR management, CI/CD operations, release management, and security monitoring using the gh CLI. Use when the user wants to manage GitHub issues, PRs, CI status, releases, contributors, stale items, or any GitHub operational task beyond simple git…
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work.
agent-github-modes
Agent skill for github-modes - invoke with $agent-github-modes.
github-automation
GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.