Borrowing it
Nothing to install: this file belongs to sponge-b0b/Polaris. 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/sponge-b0b/Polaris/main/.agents/skills/repowise/SKILL.mdgit clone --depth 1 https://github.com/sponge-b0b/PolarisWrote 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/sponge-b0b/polaris/repowise)<a href="https://agentmods.dev/skills/sponge-b0b/polaris/repowise"><img src="https://agentmods.dev/badge/skills/sponge-b0b/polaris/repowise/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/sponge-b0b/polaris/repowise"><img src="https://agentmods.dev/badge/skills/sponge-b0b/polaris/repowise.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.00049 | $0.01028 |
| Opus 5.5 | $0.00020 | $0.00411 |
| Sonnet 5.5 | $0.00010 | $0.00206 |
| Haiku 4.5 | $0.00005 | $0.00103 |
Grade A, and why
repowise 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 22d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repowise Queries Skill
Objective
Safely locate behavior, map source contexts, sweep for dead code, evaluate file brittleness, estimate change risk before modifying Python files when relevant, and recover historical rationale without reading heavy raw files into the active LLM context.
Routing Boundary
Select Repowise when the material question is where behavior lives or concerns repository status, health, hotspots, change risk, historical rationale, or dead-code triage.
Use $codebase-memory-mcp for exact structural symbols, callers/callees, dependencies, code architecture, diff blast radius, or cross-service paths; $codegraph for implicit runtime dispatch; $graphify for broad corpus/community relationships; and rg or direct reads for literals and non-code authority.
Context Inputs
- Cached discovery map:
.claude/CLAUDE.mdwhen present. - Consult it only when its cached summaries, file-page indices, or hotspot metadata materially help choose or interpret the current query. Do not preload it merely because Repowise is being used.
Guardrail Constraints
- Safety Alert Invariant: You MUST alert the user explicitly before adding code to a file flagged as highly brittle or designated as a high-risk hotspot.
- Verification Rule: Trust scoped context results, but physically verify that cited paths still exist on the local file system before editing them.
Execution Steps
Choose only the Repowise operations that answer the current material question. The capabilities below are independent, not a mandatory sequence. Do not invoke one merely because another was used. Use any combination when distinct material questions require it, and broaden when the initial evidence is insufficient.
1. Repository Scope and Orientation
When repository/module boundaries are not already known and orientation is materially useful for locating behavior or scoping a risk inquiry:
- Run:
get_overview()to inspect package trees, boundaries, and macro file distributions.
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.
- 22d ago Changed · +5 lines · +13 tokens per session f316394b2769
- 1mo ago Changed · -21 tokens per session 451c30ffcb7b
- 1mo ago First seen · 83 lines · 57 tokens per session scan A 558da2cefca3
repowise is a skill published in the GitHub repository sponge-b0b/Polaris (4 stars, last pushed today), licensed Apache-2.0. It adds 49 tokens to every session and 1,028 once invoked, about $0.0002 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-31.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
deck-retro
Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…
cwv-optimizer
Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.