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 agentmods add skills/repowise-dev/repowise/change-reviewnpx 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.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.00087 | $0.01552 |
| Opus 5 | $0.00044 | $0.00776 |
| Sonnet 5 | $0.00017 | $0.00310 |
| Haiku 4.5 | $0.00009 | $0.00155 |
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 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.
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.
- 6d 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 (6,337 stars, last pushed yesterday), licensed AGPL-3.0. It adds 87 tokens to every session and 1,552 once invoked, about $0.0004 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
scip-system-compression
Compress systems with scip-query evidence. Use to zoom out, simplify architecture, eliminate layers, consolidate commands, scripts, or helpers, find the deeper role behind unlike-looking code, build a compression atlas before a large cleanup, or execute an ordered simplification without rework.
principal-maintainability-review
Review maintainability like a principal engineer. Use when the user asks what a senior, staff, principal, or highly opinionated maintainer would notice, whether code looks vibe-coded, what is gross, what should be fundamentally different, or which architecture smells matter beyond ordinary deduplication. Finds…
scip-integrity-audit
Audit whether implementations are real with scip-query. Use for suspected faked or half-implemented features, decorative checkers or verifiers that never fail, dead code paths hidden behind graceful fallbacks, metrics that may be lying, or a "does any of this actually work" interrogation of a system.
scip-root-cause
Diagnose the design flaw behind a family of related bugs with scip-query evidence. Use when similar bugs keep recurring, the same subsystem keeps needing patches, or the user lists fixed or observed bugs and asks what is really wrong; produces a falsifiable flaw diagnosis, a latent-instance hunt, and the least…
scip-hyper-optimization
Optimize performance scientifically with current scip-query evidence. Use for benchmarking, profiling, cold or warm indexing, command latency, memory and computational cost, or comparing current-pipeline tuning with alternative designs.
scip-claim-audit
Audit output-facing status claims for evidence with scip-query. Use to classify whether an "available", "verified", "safe", "PASS", or "complete" status word is derived from a real check, hedged as a candidate, or merely asserted without being probed.