Repowise is a codebase intelligence tool that indexes source code, dependencies, history, tests, documentation, and architectural decisions to answer questions about software projects. It helps developers and coding agents understand systems, assess change impact, identify dead or risky code, and improve code health. Its catalogue add-ons extend agent workflows for using Repowise.
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 repowise-dev/repowise --skill change-reviewgit clone --depth 1 https://github.com/repowise-dev/repowiseWrote 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/repowise-dev/repowise/change-review)<a href="https://agentmods.dev/skills/repowise-dev/repowise/change-review"><img src="https://agentmods.dev/badge/skills/repowise-dev/repowise/change-review/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/repowise-dev/repowise/change-review"><img src="https://agentmods.dev/badge/skills/repowise-dev/repowise/change-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00087 | $0.01676 |
| Opus 5.5 | $0.00035 | $0.00670 |
| Sonnet 5.5 | $0.00017 | $0.00335 |
| Haiku 4.5 | $0.00009 | $0.00168 |
Grade A, and why
change-review 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 15d 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.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 15d ago Changed · +2 lines 2bf94935660b
- 19d ago Changed · +6 lines 22cb6288235a
- 21d ago Changed 00f7203197cf
- 1mo ago Changed · -1 lines ba8729a7b345
- 2mo ago First seen · 118 lines · 87 tokens per session scan A 30134bd4e94c
change-review is a skill published in the GitHub repository repowise-dev/repowise (8,052 stars, last pushed today), licensed AGPL-3.0. It adds 87 tokens to every session and 1,676 once invoked, about $0.0003 per session on Opus 5.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
scip-architecture-review
Evaluate architecture and maintainability for coding agents. Find ambiguous owners, duplicated rules, leaked coordination, misleading boundaries, and dependency problems; justify changes from behavior and consumers.
sem
Use sem for entity-level (function/class/method) code questions in any Git repo. Four questions, four verbs - where is it (sem find, sem grep), what does my change touch (sem impact), is it correct (sem check), what should a human review (sem certify). Trigger whenever the user asks where something is defined or…
sem-code-review
Find named code entities, inspect callers, and review changed functions with the locally installed Ataraxy Sem CLI. Use for code discovery or Git change review when Sem is available.
lsp-inspect
Full code quality audit for a file, package, or directory. Supports batch mode (directory walk with --top ranking), comparison mode (--diff for branch-only issues), severity calibration by blast radius, fix suggestions, and confidence tiers. Applies a check taxonomy (dead symbols, silent failures, error wrapping…
lsp-dead-code
Enumerate exported symbols in a file and surface those with zero references across the workspace. Use when auditing for dead code, cleaning up APIs, or checking which exports are safe to remove.
lsp-impact
Blast-radius analysis for a symbol or file — shows all callers, type supertypes/subtypes, and reference count before you change it. Use when refactoring, deleting, or changing the signature of any function, type, or method. Also accepts a file path to surface all exported-symbol impact in one shot.