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 blueberrycongee/Lumina-Note --skill wiki-syncgit clone --depth 1 https://github.com/blueberrycongee/Lumina-NoteWrote 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/blueberrycongee/lumina-note/wiki-sync)<a href="https://agentmods.dev/skills/blueberrycongee/lumina-note/wiki-sync"><img src="https://agentmods.dev/badge/skills/blueberrycongee/lumina-note/wiki-sync.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.1 | $0.00053 | $0.00726 |
| Opus 5 | $0.00026 | $0.00363 |
| Sonnet 5 | $0.00011 | $0.00145 |
| Haiku 4.5 | $0.00005 | $0.00073 |
Grade A, and why
wiki-sync 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 7d 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wiki synthesis playbook
Lumina maintains a wiki/ folder inside each vault that distills the user's source notes into a navigable knowledge layer. When this skill is invoked you are told the path of one source note that just changed, and your job is to update wiki/ accordingly.
Steps
-
Read the source note. Use the
readtool on the relative path you were given. Distill the key claims, definitions, and references worth surfacing — not a full copy of the note. -
Survey existing wiki entries. Use
listonwiki/to see what's already there. Useglob(wiki/**/*.md) andgrep(relevant terms) to find entries that overlap with the source note's topics. Prefer extending an existing entry over creating a new one — duplication makes the wiki worse, not better. -
Decide write strategy:
- Update existing entry: use
editfor surgical changes when the entry exists and the source adds incremental information. - Create new entry: use
writeonly when the topic genuinely has no home yet. Path:wiki/<topic-slug>.md.
- Update existing entry: use
-
Wiki file format. Every wiki entry must have:
- YAML frontmatter:
--- title: <Human-readable title> source_paths: [<rel/path/to/source.md>, ...] updated_at: <ISO 8601 timestamp> --- - When you extend an existing entry, append the source path to
source_pathsand updateupdated_at. Don't overwrite. - Body: concise prose. The wiki is a synthesis layer, not a copy. Cite source notes inline using
[[wiki link]]syntax referring to the source's relative path or title.
- YAML frontmatter:
-
Done signal. When you're finished, respond with one paragraph summarising what you changed (which wiki files updated, which created). Do not call more tools after this summary.
Constraints
- Do not run shell commands. Wiki sync runs in the background and shell access is not available.
- Stay inside the vault. Read and write paths are confined to the vault root by the agent's permission policy — going outside will fail.
- Do not delete user source notes. You may delete obsolete wiki entries you previously created (i.e., entries whose
source_pathsall point at removed notes). - Stub instead of fabricate. If the source note is empty or trivially short, write a brief stub (1–2 sentences) instead of inventing content.
- Don't add empty wiki entries. If the source has nothing worth synthesising, just say so in your summary and skip the write.
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.
- 7d ago First seen · 48 lines · 53 tokens per session scan A 247e7690ce16
wiki-sync is a skill published in the GitHub repository blueberrycongee/Lumina-Note (912 stars, last pushed 24d ago), licensed Apache-2.0. It adds 53 tokens to every session and 726 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
[object Object]
Read, search, and open notes in the user's "{{GRAPHNAME}}" Reflect graph via the reflect CLI. Use when the user asks about their notes, daily notes, journal, or anything they may have written down in Reflect.
zettelkasten-brain
A knowledge-management system based on Zettelkasten, a method of keeping small linked notes so ideas can be found and connected later. It provides tools for searching, creating, updating, reviewing, archiving, and analyzing notes.
remember:ask
Ask a natural-language question of your second brain. The AI reformulates as optimal search queries, calls the mcpremembersearchbrain tool, and synthesizes an answer with citations.
remember:status
Show Remember Second Brain statistics and status.
knowledge-base-management
A lifecycle system for managing an Obsidian knowledge base, which is a folder of linked notes. It organizes raw material, AI-maintained wiki pages, and generated views into separate layers.
okf
Author, maintain, and consume Open Knowledge Format (OKF) knowledge bundles — portable markdown + YAML frontmatter that both humans and agents read. Use when capturing project knowledge (services, APIs, schemas, metrics, runbooks, decisions) into an OKF bundle, when updating one after code or docs change, or when a…