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 agentmods add skills/gyf0311/lorekit/wiki-dailynpx skills add GYF0311/lorekit --skill wiki-dailygit 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/wiki-daily)<a href="https://agentmods.dev/skills/gyf0311/lorekit/wiki-daily"><img src="https://agentmods.dev/badge/skills/gyf0311/lorekit/wiki-daily.svg" alt="Measured on agentmods" 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 | $0.00043 | $0.02268 |
| Opus 5 | $0.00022 | $0.01134 |
| Sonnet 5 | $0.00009 | $0.00454 |
| Haiku 4.5 | $0.00004 | $0.00227 |
Grade A, and why
wiki-daily 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 5d 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 — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.
wiki-daily
目标 corpus 的 daily workflow。用于把当天想法、待办、编程决策、复盘素材先写成 inbox fragments,再按确认程度进入日编译、滚动综合、周综合或 fileback。
这是 instruction-only skill:不依赖脚本,不提供额外 references,不创建额外 skill docs。
Target config
读取 ~/.config/lorekit/daily.json。建议字段:
{
"default_corpus": "/ABSOLUTE/PATH/TO/CORPUS",
"daily_inbox_dir": "_工作台/日记收件",
"daily_archive_dir": "_归档/日记收件",
"daily_dir": "每日",
"knowledge_dir": "知识库",
"output_dir": "输出/复盘",
"journal_day_boundary": "04:00",
"timezone": "Asia/Shanghai",
"notifications": {
"enabled": false,
"channel": "lark",
"lark_user_id": "ou_xxx",
"send_on": [
"daily_compile_candidates",
"rolling_synthesis_candidates",
"weekly_synthesis_candidates"
]
}
}
若配置缺失,先让用户确认 default_corpus,不要猜测写入位置。其他字段可按上面默认值解释,但写入前仍要明确目标路径。
如果同时存在 ~/.config/lorekit/global-corpus.json 且两个配置指向不同 corpus,先报告两个目标路径并让用户确认本次 daily workflow 的目标 corpus。daily workflow 可以和 cross-project entrypoints 指向不同 corpus。
wiki-daily 可以和可选 corpus-* skills 共存:它负责目标 corpus 的日记收件箱、每日页和复盘候选;corpus-fileback 或本 skill 的 Fileback mode 只有在用户明确确认候选后才写 知识库/。
Date rule
captured_at:真实捕获时间,使用timezone中的本地时间,精确到分钟或秒。journal_date:归属日,按journal_day_boundary计算。- 默认边界是 04:00;
00:00到03:59捕获的内容属于前一个journal_date。 - 如果用户明确说"算新的一天"、"写到今天",按用户指定覆盖边界规则。
Fragment path
append / plan / review 都只创建 inbox fragment:
<default_corpus>/<daily_inbox_dir>/<journal_date>/<captured_at>-<slug>.md
fragment frontmatter 至少包含:
type: daily-entry
journal_date: YYYY-MM-DD
captured_at: YYYY-MM-DDTHH:mm:ss+08:00
source_project: <repo-or-project-name-or-null>
source_context: <short-context-or-null>
source_git_branch: <branch-or-null>
source_git_commit: <commit-or-null>
entry_type: append | plan | evening_review | project_decision | daily_compile | rolling_synthesis | weekly_synthesis
status: inbox
privacy: normal
related:
- <optional-topic>
source_project / source_context / source_git_branch / source_git_commit 用来保留当时上下文。能从当前 repo 读到就填;读不到就写 null,不要为填字段而扩大读取范围。
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.
- 5d ago First seen · 207 lines · 43 tokens per session scan A 227767178b06
wiki-daily is a skill published in the GitHub repository GYF0311/lorekit (5 stars, last pushed 1mo ago), licensed MIT. It adds 43 tokens to every session and 2,268 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…"…
release
Cut a versioned release and publish everos to PyPI via the tag-triggered workflow.
wiki-switch
Switch between multiple Obsidian wiki vault profiles. Use this skill when the user says "/wiki-switch NAME", "switch to my work wiki", "switch vault", "change wiki", "which wiki am I on", "list my wikis", "show my vaults", "create a new vault config", or "add a new wiki profile". The skill manages named config files…
llm-wiki
Build and maintain a persistent, interlinked Obsidian-compatible markdown wiki using Karpathy's LLM Wiki pattern. Extension-backed with auto-generated metadata, guardrails, and 14 custom tools (+3 opt-in agent-trajectory tools).
karpathy-llm-wiki
Use when building or maintaining a personal LLM-powered knowledge base. Triggers: ingesting sources into a wiki, querying wiki knowledge, linting wiki quality, 'add to wiki', 'what do I know about', or any mention of 'LLM wiki' or 'Karpathy wiki'.
knowledge-base-management
Obsidian 知识库全生命周期管理:三层架构、素材入库(ABC分级)、健康检查、GBrain/GraphRAG/LLM Wiki 三件套集成、目录整理.