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 skills add devin2255/repo-wiki-skill --skill repo-wikigit clone --depth 1 https://github.com/devin2255/repo-wiki-skillWrote 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/devin2255/repo-wiki-skill/repo-wiki)<a href="https://agentmods.dev/skills/devin2255/repo-wiki-skill/repo-wiki"><img src="https://agentmods.dev/badge/skills/devin2255/repo-wiki-skill/repo-wiki/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/devin2255/repo-wiki-skill/repo-wiki"><img src="https://agentmods.dev/badge/skills/devin2255/repo-wiki-skill/repo-wiki.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.00053 | $0.00997 |
| Opus 5 | $0.00026 | $0.00498 |
| Sonnet 5 | $0.00011 | $0.00199 |
| Haiku 4.5 | $0.00005 | $0.00100 |
Grade A, and why
repo-wiki 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 11d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repo Wiki
Generate a multi-page Markdown wiki for the current repository, using a built-in template derived from a scraped product wiki.
You do not need the scraped JSON at runtime: the template structure is bundled in this skill under references/.
Non-negotiables
- Grounding: All factual technical content must come from the current repo (code/config/docs). Do not invent modules, features, commands, or paths.
- Language: Output language must match the user's query language (auto-detect). If the user explicitly requests a language, that overrides auto-detection.
- No language handoff: Do not write pages that defer content to another language (e.g. “see English page for details”). The page content itself must be written fully in the target language; keep technical tokens unchanged (paths/commands/identifiers/env vars).
- Professional completeness: Follow the template page set and section checklists to produce a complete, professional wiki (overview → architecture → user guide → developer guide → reference → advanced topics).
- Style mimic (not copying): Mimic the template’s structure, tone, and section patterns. Do not copy third‑party paragraphs verbatim unless the user confirms they have rights to do so.
- Output location: Always write Markdown pages to
./.open_docsin the current project.
If the user asks to reproduce third‑party content verbatim and you are not sure they have rights to do so, refuse to copy verbatim and produce an original, repo-grounded wiki that matches the style/structure.
Template references (bundled)
- Template page set + per-page section checklist:
references/wiki-template.md - Scraped JSON format (optional, only if you want to refresh/compare):
references/wiki-json-format.md
Output
- Output directory:
./.open_docs - Always create
./.open_docs/index.mdlinking to all pages in order. - Create one Markdown file per page.
- Each page should include a navigation line that links back to
index.mdand (when applicable) the previous/next page.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 74 lines · 53 tokens per session scan A 7dee735484f0
repo-wiki is a skill published in the GitHub repository devin2255/repo-wiki-skill (11 stars, last pushed 7mo ago), licensed MIT. It adds 53 tokens to every session and 997 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…