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 ihudak/ihudak-claude-plugins --skill wiki-schemagit clone --depth 1 https://github.com/ihudak/ihudak-claude-pluginsWrote 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/ihudak/ihudak-claude-plugins/wiki-schema)<a href="https://agentmods.dev/skills/ihudak/ihudak-claude-plugins/wiki-schema"><img src="https://agentmods.dev/badge/skills/ihudak/ihudak-claude-plugins/wiki-schema/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/ihudak/ihudak-claude-plugins/wiki-schema"><img src="https://agentmods.dev/badge/skills/ihudak/ihudak-claude-plugins/wiki-schema.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.00098 | $0.03247 |
| Opus 5 | $0.00049 | $0.01623 |
| Sonnet 5 | $0.00020 | $0.00649 |
| Haiku 4.5 | $0.00010 | $0.00325 |
Grade A, and why
wiki-schema 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 3d 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 — 422 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wiki Schema — obsidian-llm-wiki
Vault knowledge schema for the wiki layer. All wiki skills read this file before operating. This is the single source of truth for conventions, boundaries, and formats.
All /wiki-* slash commands follow these conventions identically across
both Claude Code and GitHub Copilot.
Critical Boundary Rule
Wiki operations (ingest, scan, query, save, lint, hot, tags-refresh) MUST NEVER write to or delete files from:
Meetings/Daily/Projects/Customers/People/Clippings/Research/
These are Layer 1 — read-only knowledge sources. The wiki reads them; it never modifies them.
The wiki layer includes two task-management commands (/wiki-task and
/wiki-tasks-extract) that intentionally write outside the wiki directory — to
Projects/ and Tasks.md. These commands follow the task-creation rules in
_shared/task-rules.md. All other wiki operations remain wiki-directory-only.
Three-Layer Source Model
Layer 1 — Sources (read-only for wiki):
Meetings/ ← meeting notes (primary knowledge source)
Daily/ ← daily notes — extract ## Notes and ## Worklog sections only;
skip Dataview task queries (they are not content)
Projects/ ← project context, decisions, tech stack
includes Products/, Data Generators/, Jira/ subdirs
Customers/ ← customer notes
People/ ← person/team notes
Clippings/ ← web clippings
Research/ ← research notes
Layer 2 — Inbox (read + archive after processing):
.raw/ ← external sources: PDFs, exports, web clips
The ONLY directory wiki may clean up.
After successful ingest: move to .raw/_processed/YYYY-MM/
For HTML files: use defuddle if available before ingesting
npx defuddle parse <file> --md
Layer 3 — Wiki output (write exclusively here):
wiki/ ← all wiki pages and meta 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.
- 3d ago First seen · 422 lines · 98 tokens per session scan A c47c2679e1dd
wiki-schema is a skill published in the GitHub repository ihudak/ihudak-claude-plugins (2 stars, last pushed today), licensed MIT. It adds 98 tokens to every session and 3,247 once invoked, about $0.0005 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-09-05.
Other skills, from other repositories
cdb-scan
Map this codebase into project memory — a code graph of every symbol and how they connect, plus a written profile of stack, layout, conventions and workflows. Re-run any time to refresh both in place. Use when memory is newly installed on an existing project, or when the project has changed enough that the stored map…
ctx-purge
Purge the context-mode knowledge base. Permanently deletes all indexed content and resets session stats. This is destructive and cannot be undone. Trigger: /context-mode:ctx-purge.
ctx-index
Index a local file or directory into context-mode's persistent FTS5 knowledge base so future ctxsearch calls can retrieve focused snippets without rereading raw files. Trigger: /context-mode:ctx-index.
ctx-upgrade
Update context-mode from GitHub and fix hooks/settings. Pulls latest, builds, installs, updates npm global, configures hooks. Trigger: /context-mode:ctx-upgrade.
ctx-search
Search context-mode's persistent FTS5 knowledge base for previously indexed local project content, documentation, or session memory. Trigger: /context-mode:ctx-search.
evolving-status
View Self-Evolving Loop session status, history, and memory metrics.