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 yeaight7/agent-powerups --skill change-impact-checkgit clone --depth 1 https://github.com/yeaight7/agent-powerupsWrote 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/yeaight7/agent-powerups/change-impact-check)<a href="https://agentmods.dev/skills/yeaight7/agent-powerups/change-impact-check"><img src="https://agentmods.dev/badge/skills/yeaight7/agent-powerups/change-impact-check/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/yeaight7/agent-powerups/change-impact-check"><img src="https://agentmods.dev/badge/skills/yeaight7/agent-powerups/change-impact-check.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.00048 | $0.00766 |
| Opus 5 | $0.00024 | $0.00383 |
| Sonnet 5 | $0.00010 | $0.00153 |
| Haiku 4.5 | $0.00005 | $0.00077 |
Grade A, and why
change-impact-check 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 3d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Code changes rarely exist in isolation. Before declaring success, evaluate the downstream consequences of your work: what depends on what you changed, and whether those dependents still hold.
When to Use
- Before submitting a PR or marking a task complete
- You changed a public method signature, REST endpoint, or database schema
- You modified a shared utility, core helper, or widely-imported module
- You added or renamed an environment variable or config key
Inputs
- The diff of your changes (staged or committed)
- Access to the repository to search for callers and run tests
Workflow
-
Scope the diff. List what actually changed and which files are touched, so you know where to look for fallout.
git diff --stat # files changed + churn size git diff --name-only # bare list to feed into searches -
API surface. If you changed a public method signature, REST endpoint, or database schema, search the entire repository for usages of the old signature. Every caller is a potential break.
git grep -n "oldFunctionName" # all references, with line numbers git grep -nw "endpointPath" # whole-word match for a route/symbol -
Dependency graph. If you updated a core utility (e.g., a date formatter), find every module that imports it and confirm their tests still pass. Inspect the dependency tree if a third-party package version moved.
git grep -n "from '.*utils/date'" # or the ecosystem equivalent import pattern npm ls some-package # or the ecosystem equivalent dependency tree -
Configuration. If you added or renamed an environment variable, ensure it is documented in the example env file (e.g. .env.example) or the README, and that defaults exist where code reads it.
-
Act on the blast radius. If the impact is wide, run the full test suite (not just local unit tests) rather than the narrow subset, and explicitly document the affected areas in your handoff or PR description.
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.
- 3d ago First seen · 73 lines · 48 tokens per session scan A be9275eafc01
change-impact-check is a skill published in the GitHub repository yeaight7/agent-powerups (6 stars, last pushed 3d ago), licensed Apache-2.0. It adds 48 tokens to every session and 766 once invoked, about $0.0002 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-09-14.
Other skills, from other repositories
github-code-review
Review PRs: diffs, inline comments via gh or REST.
simplify-code
Sequential 3-lens cleanup of recent code changes.
requesting-code-review
Pre-commit review: security scan, quality gates, auto-fix.
kodama-constraints
Enforce non-negotiable safety, scope, security, and quality constraints for implementation and review work.
hqe
Comprehensive codebase health auditing, remediation, and verification skill based on the canonical HQE Protocol v5.0.0.
adk-review
Reviews the uncommitted changes in an adk-python working tree and reports correctness, design, public-API stability, test, sample and documentation gaps as a prioritized findings report, fixing them only when asked. Use when the user asks to review local changes, wants a self-review before opening a pull request, asks…