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 GYF0311/lorekit --skill corpus-healthgit clone --depth 1 https://github.com/GYF0311/lorekitWrote 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/gyf0311/lorekit/corpus-health)<a href="https://agentmods.dev/skills/gyf0311/lorekit/corpus-health"><img src="https://agentmods.dev/badge/skills/gyf0311/lorekit/corpus-health/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/gyf0311/lorekit/corpus-health"><img src="https://agentmods.dev/badge/skills/gyf0311/lorekit/corpus-health.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.00033 | $0.00257 |
| Opus 5 | $0.00016 | $0.00129 |
| Sonnet 5 | $0.00007 | $0.00051 |
| Haiku 4.5 | $0.00003 | $0.00026 |
Grade A, and why
corpus-health 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 9d 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.
What it actually says
corpus-health
Optional health-check gateway for a configured Lorekit corpus. It reports state and does not write knowledge.
Config
Read ~/.config/lorekit/global-corpus.json.
Required:
default_corpuslorekit_binor<default_corpus>/bin/lorekit
Use the configured corpus-local wrapper for lorekit.
Checks
From <default_corpus>, run the narrow checks needed:
<lorekit_bin> doctor --json<lorekit_bin> ingest pending
Do not run sync or mutating repair commands unless the user explicitly asks.
Output
Summarize:
- corpus path
- hard failures
- warnings
- stale indexes
- pending ingest items
- suggested next commands
Keep optional integration warnings separate from corpus hard failures.
Safety
This skill is report-only by default.
Do not modify 知识库/, 原料/, 每日/, or .wiki/ during a health check unless the user separately requests repair.
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.
- 9d ago First seen · 48 lines · 33 tokens per session scan A 922937ad4352
corpus-health is a skill published in the GitHub repository GYF0311/lorekit (5 stars, last pushed 1mo ago), licensed MIT. It adds 33 tokens to every session and 257 once invoked, about $0.0002 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-31.
Other skills, from other repositories
mindbase
Maintain a persistent AI-tended research wiki. Activates when the user wants to ingest a source (PDF, URL, article, paste), capture a thought, build the wiki context, query what's already known, lint for orphans/contradictions, or maintain page conventions. Phrases include "add this to my wiki", "today I decided…"…
wiki-ingest
Ingest exactly one research paper or source document into an open-llm-wiki vault. Use when the user explicitly asks to add, ingest, process, or publish a paper into the wiki. The workflow parses the source, drafts a source page, runs independent QA, publishes only after the quality gate passes, extracts and normalizes…
query-writeback
Answer cross-source questions about an open-llm-wiki vault and optionally write reusable synthesis back into concept pages. Use when the user asks a wiki question that requires comparing, connecting, or tracing multiple source/concept pages. By default answer first and propose writeback; modify files only when the…
wiki-lint
Run a health check for an open-llm-wiki vault. Use when the user asks to lint, audit, validate, or periodically check wiki quality. The default mode is report-only: inspect schema compliance, QA coverage, links, stale claims, contradictions, and log health. Modify files only when the user explicitly requests fix mode…
zenwiki-ask
Search this local ZenWiki and answer questions about its content with citations. Use this whenever the user asks anything about wiki topics — what / how / why / compare / list / which — that might be answered by pages under wiki/. Always run zenwiki search first; never answer from memory.
openkb-deck-neon
A skill for creating a single-file HTML slide deck from content stored in OpenKB, a knowledge-base chat system. It defines a dark, high-tech visual style using neon colors, glow effects, and glass-like panels.