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/sistema2d/framecode-vibework/wiki-curatornpx skills add Sistema2D/FrameCode-VibeWork --skill wiki-curatorgit clone --depth 1 https://github.com/Sistema2D/FrameCode-VibeWorkWrote 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/sistema2d/framecode-vibework/wiki-curator)<a href="https://agentmods.dev/skills/sistema2d/framecode-vibework/wiki-curator"><img src="https://agentmods.dev/badge/skills/sistema2d/framecode-vibework/wiki-curator.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.00013 | $0.01125 |
| Opus 5 | $0.00006 | $0.00562 |
| Sonnet 5 | $0.00003 | $0.00225 |
| Haiku 4.5 | $0.00001 | $0.00112 |
Grade A, and why
wiki-curator 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 6d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SKILL: Wiki Curator
Maintain the LLM Wiki as a continuously improving knowledge base while preserving FCVW's pillars: updates on demand, measurable freshness, and low token cost.
Purpose
Promote sourced reusable knowledge into the smallest canonical wiki surface without duplicating records or loading the full archive by default.
Activation Triggers
Load this skill when a task involves:
- creating, updating, merging, or reviewing wiki knowledge;
- promoting plans, changelogs, troubleshooting, audits, decisions, or sessions into reusable wiki pages;
- grouping related notes under the same topic;
- organizing tags, themes, or frontmatter colors;
- checking stale, duplicated, contradictory, or superseded wiki content;
- preparing minor or major releases that add reusable knowledge.
Inputs
Changed source records, current canonical page candidates, wiki/schema.md, taxonomy, metrics, active index/log, typed relationship findings, stale-source review candidates, and an explicit source-bounded search scope.
Fixed Cost Mode
Always use the standard optimized mode. Do not ask the user to choose a cost mode.
Load only:
AGENTS.mdchecklist summary.CONTEXT_MAP.mdrow for the active session type.wiki/index.md,wiki/log.md,wiki/schema.md.wiki/taxonomy.mdandwiki/metrics.mdwhen theme, color, tag, or freshness decisions are needed.- Source files that directly triggered the curation: changed plans, changelogs, troubleshooting records, audits, decisions, sessions, or specific wiki pages.
Do not read every wiki page unless wiki-lint reports an anomaly that requires it.
Curation Loop
- Collect trigger sources: identify new or changed source records and load only their summaries or relevant sections.
- Decide promotion: promote only knowledge that meets
wiki/schema.mdpromotion criteria. - Merge before create: update an existing related page when the topic already exists; create a new page only for a distinct reusable concept.
- Cluster topics: link related pages with Obsidian-style links and record canonical pages for superseded or overlapping notes.
- Refresh metadata: set
last_reviewed,related_version,tags,theme,theme_color,maturity, andnext_reviewwhen applicable; do not require maturity for source, raw, or session records. - Use typed relations deliberately: prefer the narrowest meaningful relation, resolve every target, and rely on generated inverse edges instead of copying both directions.
- Review changed sources: when a tracked
source_digestchanges, inspect only pages linked throughderived_from; confirm, update, supersede, or invalidate them before refreshing the digest. - Update metrics: record freshness, promotion, duplication, source-impact, and taxonomy results in
wiki/metrics.mdor the active plan. - Log curation: append a compact event to
wiki/log.md. - Validate: run deterministic
wiki-lintfor minor/major releases or when three or more wiki pages changed; semantic review remains optional and source-bounded.
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.
- 6d ago First seen · 105 lines · 13 tokens per session scan A c82cc5ce6d4a
wiki-curator is a skill published in the GitHub repository Sistema2D/FrameCode-VibeWork (23 stars, last pushed 5d ago), licensed Apache-2.0. It adds 13 tokens to every session and 1,125 once invoked, about $0.0001 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
evaluate-pattern-adoption
Run or plan this repository's pattern-adoption evidence evaluation locally with signed-in Codex agents. Use when asked to refresh stale evidence, assess stable or exploratory patterns, evaluate one or all catalog patterns, discover possible new patterns, or prepare a reviewable evidence PR without model-backed GitHub…
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).
braindb
Memory recall and save. Use at every conversation start and whenever the user shares personal information, expertise, project context, preferences, or decisions worth remembering long-term.
braindb-agent
Persistent memory across sessions via the BrainDB agent. Use at conversation start and whenever you need to recall what you know about the user or save new information to long-term memory.
braindb-custom-profile
How to author a BrainDB custom profile — prompt add/replace fragments and an optional keyless ingestor — that shapes wiki naming/structure and feeds a custom ingestion source, with zero effect on defaults when inactive.
consolidate
Consolidate raw captures into durable entity/topic pages (Axis 1, Track C): review recent meetings / daily / transcripts and PROMOTE their substance into the higher-order wiki — create the page for a person mentioned but never filed, refresh a topic page a fresher note left behind, weave the backlinks. A deterministic…