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.00057 | $0.00933 |
| Opus 5 | $0.00028 | $0.00466 |
| Sonnet 5 | $0.00011 | $0.00187 |
| Haiku 4.5 | $0.00006 | $0.00093 |
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 9d 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 — 83 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 blast radiuses before modifying any Python files, and to answer structural questions about the project codebase without reading heavy raw files into the active LLM context.
Context Inputs
- Authoritative Cache Map:
.claude/CLAUDE.md. - Before executing any lookup tool, reference this cached markdown segment to evaluate system summaries, file page indices, and pre-calculated hotspots.
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
When investigating existing Python functionality or assessing change risks, run the Repowise tools sequentially based on your investigative intent:
1. Repository Scopes & High-Level Architecture
Before diving into code blocks, establish the high-level boundaries of the module or repository layer:
- Run:
get_overview()to inspect package trees, boundaries, and macro file distributions.
2. Behavior Location & Semantic Search
Locate specific code strings, definitions, or architectural concepts across the repository:
- Run:
get_answer()orsearch_codebase()
3. Context & Structural Cleanliness Isolation
Extract exact, bounded code blocks and symbol trees while ensuring you are not adding code to abandoned or orphaned logic branches:
- Run:
get_context()andget_symbol()to isolate active implementation code. - Run:
get_dead_code()to verify that the functions, classes, or files you are touching are actively used and have not been abandoned.
4. Structural Risk Assessment
Check the target destination for maintenance hazards and unexpected system coupling to ensure safe modification:
- Run:
get_healthto evaluate target-file biomarkers. - Run:
get_risk()to isolate hotspots, hidden structural coupling, and change blast radius.
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.
- 9d 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 57 tokens to every session and 933 once invoked, about $0.0003 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-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.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
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…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.