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 u9401066/rootcause-mcp --skill llm-wiki-buildergit clone --depth 1 https://github.com/u9401066/rootcause-mcpWrote 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/u9401066/rootcause-mcp/llm-wiki-builder)<a href="https://agentmods.dev/skills/u9401066/rootcause-mcp/llm-wiki-builder"><img src="https://agentmods.dev/badge/skills/u9401066/rootcause-mcp/llm-wiki-builder/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/u9401066/rootcause-mcp/llm-wiki-builder"><img src="https://agentmods.dev/badge/skills/u9401066/rootcause-mcp/llm-wiki-builder.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.00034 | $0.00350 |
| Opus 5 | $0.00017 | $0.00175 |
| Sonnet 5 | $0.00007 | $0.00070 |
| Haiku 4.5 | $0.00003 | $0.00035 |
Grade A, and why
llm-wiki-builder 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 8d 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.
This is a copy
92% identical to llm-wiki-builder — 3 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
LLM Wiki Builder
Use this skill when the user asks to create, refresh, repair, or extend a Foam wiki or LLM-readable literature wiki.
Read First
.clinerules/35-foam-llm-wiki.md.clinerules/workflows/llm-wiki-build.md.github/zotero-research-workflow.mdwhen Zotero or PubMed evidence is involved
Multi-Tool Choreography
- Inspect the filesystem for the wiki root, Foam markers, existing note style, and link conventions.
- Use Zotero tools to inspect saved library items, collections, and duplicate state before importing or refetching.
- Use PubMed Search MCP tools for discovery, article details, related/citing articles, references, exports, persistent Research Chronicle, and full-text follow-up.
- Use asset-aware or document tools when PDFs, DOCX, DFM, tables, figures, or span-level citations are part of the request.
- Write or update Markdown notes with Foam-compatible wikilinks and preserved source identifiers.
- Validate generated links and report unresolved wiki TODOs separately from completed notes.
Output Contract
- Keep the note graph readable in Foam and useful for LLM retrieval.
- Preserve source provenance close to claims.
- Ask before bulk rewrites, destructive cleanup, or Zotero imports.
- Do not leave broken wikilinks hidden in generated files.
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.
- 8d ago First seen · 39 lines · 34 tokens per session scan A 726a5c27dd51
llm-wiki-builder is a skill published in the GitHub repository u9401066/rootcause-mcp (0 stars, last pushed 6d ago), licensed Apache-2.0. It adds 34 tokens to every session and 350 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to llm-wiki-builder, differing in 3 lines, and is treated as a copy.
Other skills, from other repositories
pdf-processing
Extract text from PDFs, fill forms, and merge documents.
extracting-lab-tables
Detects and extracts tabular laboratory panels from PDFs, scans, and images into structured rows ready for OpenMed and FHIR. Use when the user has a CBC, CMP, lipid panel, or other lab report as a scanned image / PDF / spreadsheet and needs the test name, value, unit, reference range, and abnormal flag as clean rows.…
structuring-radiology-reports
Converts free-text radiology narratives into structured findings and impression — with measurements, laterality, anatomy, and follow-up recommendations — after OpenMed NER. Use when the user has a CT/MRI/X-ray/ultrasound/mammography report and needs the sections split (technique, comparison, findings, impression)…
ingesting-clinical-documents
Turn scanned faxes, images, and CSV/CDA exports into clean text ready for OpenMed de-identification and NER, fully on-device. Use when the user has clinical documents (image scans, photographed/faxed notes, tabular CSV/TSV exports, C-CDA XML) and needs OCR or structured intake before openmed.deidentify and…
parsing-ccda-documents
Parses C-CDA / CCD XML clinical documents to extract human-readable section narrative plus coded entries, keyed by section LOINC codes and templateIds. Use before OpenMed processing when ingesting C-CDA R2.1 documents (CCD, Discharge Summary, H&P, Consultation Note) exported from an EHR and you need the narrative…
summarizing-clinical-notes
Produces structured, citation-anchored summaries of clinical notes — one-liner, hospital course, and problem-oriented views — where every claim cites a source span so nothing is hallucinated. Use after de-identifying notes when the user wants a discharge summary draft, handoff/SBAR, problem list, or chart-abstraction…