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-ingestgit 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-ingest)<a href="https://agentmods.dev/skills/ihudak/ihudak-claude-plugins/wiki-ingest"><img src="https://agentmods.dev/badge/skills/ihudak/ihudak-claude-plugins/wiki-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/ihudak/ihudak-claude-plugins/wiki-ingest"><img src="https://agentmods.dev/badge/skills/ihudak/ihudak-claude-plugins/wiki-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.00088 | $0.01466 |
| Opus 5 | $0.00044 | $0.00733 |
| Sonnet 5 | $0.00018 | $0.00293 |
| Haiku 4.5 | $0.00009 | $0.00147 |
Grade A, and why
wiki-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 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.
How it starts
The opening of the file, as written. The whole thing — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
wiki-ingest
Read skills/wiki-schema/SKILL.md fully before proceeding.
Invoke with: /wiki-ingest @filepath
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).
All file paths in this skill are relative to the vault root.
Step 2 — Delta check
Read wiki/_manifest.json (create it from the schema template if it does not
exist yet).
Compute the source file hash:
md5sum "<filepath>" | cut -d' ' -f1
If the path exists in _manifest.json with the same hash: stop and report
Already ingested (unchanged). Use 'force' keyword to re-ingest.
Proceed if: path is absent, hash differs, or user said force.
Step 3 — Read the source file completely
Do not skim. Read every section.
Step 4 — Identify file type and extract accordingly
| Path prefix | Type | What to extract |
|---|---|---|
Meetings/ |
Meeting note | Decisions made, technologies discussed, action items (flag them — do NOT create tasks directly; /wiki-tasks-extract consumes these flags later), people present, open questions |
Daily/ |
Daily note | ## Notes and ## Worklog sections only. Skip all Dataview/Obsidian Tasks query blocks — those are not content |
Projects/ |
Project file | Tech stack, decisions, key links, patterns discovered, status |
Customers/ |
Customer note | Use cases, pain points, customer context, integrations mentioned |
People/ |
Person note | Role, team, expertise areas, relationships |
Clippings/ or Research/ |
Research/clip | Key concepts, takeaways, relevant decisions |
.raw/ |
Inbox source | Full extraction — this is a deliberate ingest target; extract everything |
Note: Daily notes must use level-2
## Notesand## Worklogheadings; other heading levels are skipped.
For .raw/ HTML files: check if defuddle is available first:
npx defuddle --version 2>/dev/null && echo "available" || echo "not available"
If available: npx defuddle parse "<filepath>" --md and use that output.
If not: read the file directly.
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 · 174 lines · 88 tokens per session scan A 6810faa25bec
wiki-ingest is a skill published in the GitHub repository ihudak/ihudak-claude-plugins (2 stars, last pushed today), licensed MIT. It adds 88 tokens to every session and 1,466 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
dummy-dataset
Generate realistic dummy datasets for testing with customizable columns, constraints, and output formats (CSV, JSON, SQL, Python script). Use when creating test data, building mock datasets, or generating sample data for development and demos.
stakeholder-map
Build a stakeholder map using a power/interest grid, identify communication strategies per quadrant, and generate a communication plan. Use when managing stakeholders, preparing for a launch, aligning cross-functional teams, or planning stakeholder engagement.
competitive-battlecard
Create sales-ready competitive battlecards comparing your product against a specific competitor — positioning, feature comparison, objection handling, and win/loss patterns. Use when preparing sales teams, creating competitive materials, or responding to 'why not competitor X?'.
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".
sheet-music-publisher
Converts mastered audio to sheet music and creates printable songbooks. Use after mastering when the user wants sheet music or a songbook for their album.
bun-test-mocking
Use for mock functions in Bun tests, spyOn, mock.module, implementations, and test doubles.