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 staruhub/ClaudeSkills --skill llm-wikigit clone --depth 1 https://github.com/staruhub/ClaudeSkillsWrote 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/staruhub/claudeskills/llm-wiki)<a href="https://agentmods.dev/skills/staruhub/claudeskills/llm-wiki"><img src="https://agentmods.dev/badge/skills/staruhub/claudeskills/llm-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/staruhub/claudeskills/llm-wiki"><img src="https://agentmods.dev/badge/skills/staruhub/claudeskills/llm-wiki.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00102 | $0.01553 |
| Opus 5 | $0.00051 | $0.00776 |
| Sonnet 5 | $0.00020 | $0.00311 |
| Haiku 4.5 | $0.00010 | $0.00155 |
Grade A, and why
llm-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 10d 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LLM Wiki for Codebases
Build a persistent, interlinked markdown wiki that captures the architecture, modules, patterns, and APIs of a codebase. The wiki lives in .llm-wiki/ at the project root. Humans curate and direct; the LLM handles all bookkeeping.
Based on Andrej Karpathy's LLM Wiki pattern: raw sources are "compiled" into a structured wiki that compounds over time.
Mode Detection
Determine the mode based on current state:
- No
.llm-wiki/directory exists -> Full Build mode .llm-wiki/exists -> Update mode (diff and refresh)
Full Build Workflow
Phase 1: Reconnaissance
- Read top-level files: README, package.json/Cargo.toml/go.mod/pyproject.toml/build.gradle etc.
- Run
findor Glob to map the directory tree (ignore node_modules, .git, vendor, dist, build, pycache, .venv) - Identify: language(s), framework(s), build system, entry point(s), test framework
- Count files per directory to gauge module boundaries
- Read CLAUDE.md / AGENTS.md / .cursor/rules if present - they contain valuable architectural context
Record findings in .llm-wiki/_schema.md (see references/wiki-schema.md for format).
Phase 2: Skeleton
Create the directory structure:
.llm-wiki/
_schema.md # Wiki conventions and project metadata
_index.md # Content-oriented catalog by category
_log.md # Chronological build/update log
architecture/ # High-level design docs
modules/ # Per-module deep dives
concepts/ # Cross-cutting concepts (auth, caching, error handling...)
apis/ # API surface docs (REST endpoints, CLI commands, exported functions)
guides/ # How-to guides (setup, deployment, testing)
Phase 3: Core Articles
Write articles in priority order. See references/article-templates.md for templates.
Priority 1 - Architecture:
architecture/overview.md- System architecture, component diagram (ASCII), tech stackarchitecture/data-flow.md- How data flows through the systemarchitecture/directory-structure.md- Annotated directory tree
What ships with it
2 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.
- 10d ago First seen · 146 lines · 102 tokens per session scan A 31196d847bb7
llm-wiki is a skill published in the GitHub repository staruhub/ClaudeSkills (712 stars, last pushed 28d ago), licensed MIT. It adds 102 tokens to every session and 1,553 once invoked, about $0.0005 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
report-helper
A Chinese-language research workflow that searches the internet and produces a formatted PDF report about a specified topic.
giasip-dispatch
A skill for sending a task to other AI models and collecting their results. It supports direct API calls, command-line tools and built-in internal agents, depending on the model.
searchcans-deep-research
Conduct bounded, evidence-led, account-aware web research with SearchCans SERP API and Reader API. Use for cited-source research that needs current localized web evidence, such as market, competitor, technology, policy, company, or product research; plan 3–5 subquestions, set a source budget, read selected pages…
searchcans-serp-content-gap
Analyze a current, geo-targeted Google or Bing SERP with SearchCans and turn observed result features, People Also Ask questions, related searches, knowledge graph, and news signals into an evidence-backed, account-aware content decision brief. Use for localized SEO/GEO planning, keyword research, competitor-page…
searchcans-market-watch
Build a current, geo-targeted market-watch snapshot from Google Search, Google News, Bing Search, and selected Reader extracts. Use for competitor and category monitoring, PR/news tracking, launch intelligence, and URL-level change checks between two bounded runs; reject malformed, placeholder, or un-attributable News…
searchcans-product-serp-brief
Create a localized product-search evidence brief from Google Shopping, Google web results, Google Images, and optional Reader extracts of explicit merchant URLs. Use for e-commerce category research, competitor assortment discovery, product-page planning, and market-specific merchandising briefs.