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-hotgit 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-hot)<a href="https://agentmods.dev/skills/ihudak/ihudak-claude-plugins/wiki-hot"><img src="https://agentmods.dev/badge/skills/ihudak/ihudak-claude-plugins/wiki-hot/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-hot"><img src="https://agentmods.dev/badge/skills/ihudak/ihudak-claude-plugins/wiki-hot.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.00081 | $0.00547 |
| Opus 5 | $0.00041 | $0.00273 |
| Sonnet 5 | $0.00016 | $0.00109 |
| Haiku 4.5 | $0.00008 | $0.00055 |
Grade A, and why
wiki-hot 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.
What it actually says
wiki-hot
Read skills/wiki-schema/SKILL.md fully before proceeding.
Invoke with: /wiki-hot
Step 1 — Resolve VAULT_PATH
Vault path: ~/obsidian_vault by default; set VAULT_PATH to override. WSL users with a Windows-side vault must set VAULT_PATH explicitly (e.g. /mnt/c/Users/<name>/obsidian_vault).
Step 2 — Read recent activity
- Read the last 10 entries of
wiki/_log.md(top of file — newest first). - Read
wiki/_index.mdto understand current wiki scope. - For any pages created or updated in the last 3 log entries: read those pages.
Step 3 — Write hot.md
Overwrite wiki/hot.md completely with a fresh summary following the format
from wiki-schema:
---
type: meta
title: "Hot Cache"
updated: YYYY-MM-DDTHH:MM:SS
---
# Recent Context
## Last Updated
YYYY-MM-DD. [One sentence: what the most recent wiki activity was]
## Key Recent Facts
- [Most important recent knowledge in the wiki]
- [Second most important]
- [Third, only if genuinely significant]
## Recent Changes
- Created: [[list of recently created pages]]
- Updated: [[list of recently updated pages]]
- Flagged: [any unresolved contradictions or open issues, or "none"]
## Active Threads
- [Current research topic or work in progress, based on log]
- [Open question not yet resolved, or "none identified"]
Constraints:
- Total file length: ≤300 words. Cut ruthlessly.
- Focus on what is most likely to be useful at the start of the next session.
- Do not narrate the full log history. Synthesise.
Step 4 — Append to _log.md
## [YYYY-MM-DD] hot | manual refresh
Finish
Hot cache refreshed. wiki/hot.md updated (YYYY-MM-DD).
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 · 85 lines · 81 tokens per session scan A 821842ce3ff0
wiki-hot is a skill published in the GitHub repository ihudak/ihudak-claude-plugins (2 stars, last pushed today), licensed MIT. It adds 81 tokens to every session and 547 once invoked, about $0.0004 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
memory
Recall applicable reviewed topic pages or maintain them through separately budgeted mining, learning and curation. Triggers: "memory", "recall prior work", "mine and learn", "curate memory", "qualify or retire a lesson".
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-search
Search context-mode's persistent FTS5 knowledge base for previously indexed local project content, documentation, or session memory. Trigger: /context-mode:ctx-search.
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.