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 songzhuozhu/obsidian-llm-wiki --skill approve_ingestgit clone --depth 1 https://github.com/songzhuozhu/obsidian-llm-wikiWrote 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/songzhuozhu/obsidian-llm-wiki/approve_ingest)<a href="https://agentmods.dev/skills/songzhuozhu/obsidian-llm-wiki/approve_ingest"><img src="https://agentmods.dev/badge/skills/songzhuozhu/obsidian-llm-wiki/approve_ingest/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/songzhuozhu/obsidian-llm-wiki/approve_ingest"><img src="https://agentmods.dev/badge/skills/songzhuozhu/obsidian-llm-wiki/approve_ingest.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.00031 | $0.00482 |
| Opus 5 | $0.00015 | $0.00241 |
| Sonnet 5 | $0.00006 | $0.00096 |
| Haiku 4.5 | $0.00003 | $0.00048 |
Grade A, and why
approve_ingest 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 13d 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
approve_ingest
Use this skill after the user confirms that a pending_review ingest unit is ready to be archived into inspool-wiki-en/raw/processed/.
Steps
- Read
inspool-wiki-en/AGENTS.md. - Review
inspool-wiki-en/raw/index.mdandinspool-wiki-en/wiki/log.md. - Scan
inspool-wiki-en/raw/unprocessed/. - Find ingest units marked
pending_review. - If the user specified a batch, process that batch. Otherwise, prioritize the most recent
pending_reviewbatch. - Verify that the related wiki pages and
processed_intofields exist. - Record the old and target path for each raw file in the ingest unit.
- Update workflow fields for each raw file, for example:
processing_status: processedreviewed_at: <today>processed_at: <today>
- Move the raw files into
inspool-wiki-en/raw/processed/. - Repair old raw references in source pages and other wiki pages, including:
raw_notein frontmatter- the "raw material" link under source information
- any hard-coded
raw/unprocessed/...path strings
- Run a localized self-check and confirm that
inspool-wiki-en/wiki/no longer contains those stale paths. - Update
inspool-wiki-en/raw/index.md. - Append an
approvelog entry toinspool-wiki-en/wiki/log.md.
Constraints
- run this only after explicit user confirmation
- do not substantially rewrite wiki prose during approval
- path repair is required when raw files move
- if the self-check fails, list the stale paths explicitly instead of pretending the archive succeeded
- if the
pending_reviewbatch does not match current wiki records, report the mismatch first
Output
- state which ingest unit you are archiving
- list which raw files moved into
processed/ - state clearly whether the stale-path check passed
- explain the reason if archiving did not complete
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.
- 13d ago First seen · 46 lines · 31 tokens per session scan A c17840418c5d
approve_ingest is a skill published in the GitHub repository songzhuozhu/obsidian-llm-wiki (121 stars, last pushed 4mo ago), licensed MIT. It adds 31 tokens to every session and 482 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…