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/codebase-explorationnpx skills add repowise-dev/repowise --skill codebase-explorationgit clone --depth 1 https://github.com/repowise-dev/repowiseWhat 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 | $0.00081 | $0.00988 |
| Opus 5 | $0.00041 | $0.00494 |
| Sonnet 5 | $0.00016 | $0.00198 |
| Haiku 4.5 | $0.00008 | $0.00099 |
Grade A, and why
codebase-exploration 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 yesterday.
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.
- yesterday First seen · 67 lines · 81 tokens per session scan A 310976100457
codebase-exploration is a skill published in the GitHub repository repowise-dev/repowise (6,273 stars, last pushed yesterday), licensed AGPL-3.0. It adds 81 tokens to every session and 988 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-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-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.
principal-maintainability-review
Review maintainability like a principal engineer. Use when the user asks what a senior/staff/principal maintainer would notice, whether code looks vibe-coded, what is gross, what should be fundamentally different, or which architecture smells matter beyond ordinary deduplication.
scip-system-compression
Compress systems with SCIP evidence. Use to zoom out, simplify architecture, eliminate layers, consolidate commands/scripts/helpers, find deeper roles, reason about same-in-principle repetition, build a compression atlas, or execute ordered simplification.
scip-explore
Understand a repository system end to end before explaining, planning, changing, or reviewing it. Use when the task depends on how behavior enters the system, branches, transforms data, crosses runtimes, changes state, reaches consumers, or recovers from failure across multiple symbols or files. Apply scip-query as…
scip-query
Use FIRST for codebase work when compiler-resolved identity, runtime boundaries, callers, dependencies, consumers, architecture, change impact, or cleanup relationships can affect the answer. It exposes exact referents, explicit typed-graph projections, and source evidence; it does not infer task relevance. Pair it…