repowiki-exploration

repowiki-exploration is a skill for Claude Code, Codex from BuildrAI/Buildr. It costs 52 tokens per session (755 once invoked), scanned A, original, MIT.

A codebase-exploration guide that turns source code, configuration, and existing documents into a structured explanation of a project’s purpose, responsibilities, relationships, and design choices.

In plain words
What is it for?
Use it to get an overview, trace a real user scenario, or investigate one component and its boundaries. It can also help maintain focused, evidence-based project knowledge.
Why use it?
It helps people understand an unfamiliar project without reading every file or treating old documentation as automatically correct. It also separates verified facts from assumptions and unknowns.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to get an overview, trace a real user scenario, or investigate one component and its boundaries. It can also help maintain focused, evidence-based project knowledge.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/buildrai/buildr/repowiki-exploration
Install

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.

Any agent
npx skills add BuildrAI/Buildr --skill repowiki-exploration
Clone the repo
git clone --depth 1 https://github.com/BuildrAI/Buildr

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for repowiki-exploration

README.md
[![agentmods](https://agentmods.dev/badge/skills/buildrai/buildr/repowiki-exploration/github.svg)](https://agentmods.dev/skills/buildrai/buildr/repowiki-exploration)
Your own site
<a href="https://agentmods.dev/skills/buildrai/buildr/repowiki-exploration"><img src="https://agentmods.dev/badge/skills/buildrai/buildr/repowiki-exploration/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.

agentmods 80×15 button for repowiki-exploration

Your own site · 80×15
<a href="https://agentmods.dev/skills/buildrai/buildr/repowiki-exploration"><img src="https://agentmods.dev/badge/skills/buildrai/buildr/repowiki-exploration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 52 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 755 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00052 $0.00755
Opus 5.5 $0.00021 $0.00302
Sonnet 5.5 $0.00010 $0.00151
Haiku 4.5 $0.00005 $0.00076

Measured 1mo ago against content hash e243fc074bc3, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

repowiki-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 1mo 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.

projects/product/openspec/changes/archive/2026-09-23-reshape-project-knowledge-exploration/experiments/repowiki-exploration/SKILL.md · 40 lines

What it actually says

项目结构探索试用

这是从 RepoWiki 可见产物重建并收窄的试用方法,依据与推断见 逆向证据。目标是让人能够理解和判断软件;实际事实来自当前规范、代码、配置及已确认决定。

选择当前问题

沿用用户给出的项目或服务范围。看全貌时从目的、主要职责与关键关系开始;跟场景时选择一个真实目标,沿参与者、过程和结果调查;深入某部分时关注它的责任、依赖和边界。用户只需表达问题,无需列出文件或先掌握术语。

区分只读理解与长期建设。普通提问以解释为成果;用户明确要求建设或完善时,才维护指定范围的知识文件。已有建设授权持续有效。

调查结构与依据

  1. 读取已有导航和主要声明,按职责识别相关部分及代码范围;目录与旧文档用于定位,不自动视为正确模型。
  2. 围绕当前问题检查关键关系:谁负责什么、谁调用谁、数据或结果由谁保存、哪些条件影响行为。用实际来源核实,会影响结论的疑点再深入。
  3. 设计原因查找规范、决策或已确认材料。来源只证明实现时,将原因标为推断或未知;冲突分别保留双方依据。
  4. 关键职责、关系与重要边界已有依据,未知明确且有进一步定位入口时,停止本轮展开。系统探索不要求读完所有代码;记录未覆盖范围。

调查可以深入函数,解释仍按人的当前判断选择粒度。不要把调查顺序或每个文件分别写成文章。

组织解释

围绕问题给出直接结论和有意义的结构。按实际关系选择职责表、对象关系图、流程或状态视图;简单线性过程使用文字即可。每条连线说明具体含义,引用可定位到实际依据。复用适用的现有视图。

优先保留目标、重要关系、行为约束及有依据的取舍。字段、具体函数和随时可查的步骤,在它们影响当前判断或具有反复参考价值时才展开。不设固定章节、篇数、层级或图数。

在当前主题旁给出少量具体的继续探索问题,让不熟悉项目的人能够选择下一步。来源和深入资料保持可达,不把完整来源清单挤进主线。

建设长期成果时优先完善唯一正文及必要导航。精简前核对独有事实和设计理由的去向;详细参考可以按需阅读。普通追问不会自动新增永久文章。

核对成果

逐项检查:解释是否足以说明当前目标、主要职责、关键过程及判断边界;关系是否与来源一致;未知是否明示;继续探索问题是否具体且能找到依据。实际修改文件时检查链接和适用展示。

交付实际解释或文件、重要依据、覆盖与未覆盖范围。区分静态核对、试用结果和人的验收,不用生成成功证明用户已经理解。

Changes

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.

  1. 1mo ago First seen · 40 lines · 52 tokens per session scan A e243fc074bc3

Subscribe to this mod's changes

repowiki-exploration is a skill published in the GitHub repository BuildrAI/Buildr (28 stars, last pushed yesterday), licensed MIT. It adds 52 tokens to every session and 755 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-09-25.

Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

component-fixtures

Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.

microsoft/vscode · 53 tokens