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/abstractwebunit/markdown-publish-plugin/publish-vaultnpx skills add abstractwebunit/markdown-publish-plugin --skill publish-vaultgit clone --depth 1 https://github.com/abstractwebunit/markdown-publish-pluginWrote 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/abstractwebunit/markdown-publish-plugin/publish-vault)<a href="https://agentmods.dev/skills/abstractwebunit/markdown-publish-plugin/publish-vault"><img src="https://agentmods.dev/badge/skills/abstractwebunit/markdown-publish-plugin/publish-vault.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 | $0.00091 | $0.01666 |
| Opus 5 | $0.00046 | $0.00833 |
| Sonnet 5 | $0.00018 | $0.00333 |
| Haiku 4.5 | $0.00009 | $0.00167 |
Grade A, and why
publish-vault 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 4d 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 — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Publish a Markdown / Obsidian vault to GitHub Pages
Turn a folder of Markdown notes (an Obsidian vault) into a live, searchable
website. The whole thing runs in the user's own GitHub account — a new
public repo, a GitHub Actions workflow that builds with the published
markdown-publish engine, and GitHub Pages hosting. No backend, no cost.
Golden rules
- Never create a repo or push anything before the user explicitly confirms the plain-language config summary in step 3.
- Use smart defaults; only ask the user when something can't be inferred.
- Verify each step before moving on. If a step fails, stop and surface the real error — don't paper over it.
Preconditions
The skill drives the gh CLI and git. Before anything else:
- Check
ghis installed and authenticated: rungh auth status.- If not authenticated, tell the user to run
! gh auth loginthemselves (the!prefix runs it in the session), then re-check. The token needsrepoandworkflowscopes.
- If not authenticated, tell the user to run
- Capture their GitHub login for URLs:
gh api user -q .login.
Flow
1. Locate the vault
Find the folder of Markdown notes. If the user didn't say where it is, ask once.
Confirm it looks like a vault (contains .md files; an Obsidian vault may also
have .canvas files and a .obsidian/ folder). Resolve its absolute path.
2. Resolve config (smart defaults, no questions yet)
| Field | Default |
|---|---|
repo |
the vault folder name, slugified (lowercase, dashes) |
siteName |
the vault folder name, human-cased |
lang |
autodetect; fall back to en |
home |
leave empty (engine auto-detects a welcome/index note) |
baseHref |
/<repo>/ ← load-bearing, see note below |
base-href is load-bearing. GitHub Pages project sites serve under
https://<login>.github.io/<repo>/. The build must use base href/<repo>/or every asset and link 404s. Always set it.
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.
- 4d ago First seen · 198 lines · 91 tokens per session scan A 9ef6b5e477fd
publish-vault is a skill published in the GitHub repository abstractwebunit/markdown-publish-plugin (0 stars, last pushed 2mo ago), licensed MIT. It adds 91 tokens to every session and 1,666 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-08-31.
Other skills, from other repositories
api-workers
Cloudflare Workers deployment using createWorkerHandler from @cyanheads/mcp-ts-core/worker. Covers the full handler signature, binding types, CloudflareBindings extensibility, runtime compatibility guards, and wrangler.toml requirements.
deeppapernote
Generate a high-quality deep-reading note for a single paper and write it into an Obsidian-style vault. Use when the user gives a paper title, DOI, URL, arXiv ID, Zotero item, or local PDF and wants a polished Markdown note with strong structure, evidence-based analysis, and figure placeholders.
cloud-administration
Administers the cloud the company runs on rather than the one it sells — tenant and subscription structure, the SaaS estate and who owns each app, identity as the real perimeter, cloud spend that arrives as a surprise, and what the provider does not do for you. Use this to structure subscriptions or tenants, get…
network-administration
Designs and operates the corporate network — segmentation, remote access, wireless, DNS and addressing, and diagnosing network problems. Use this to segment a network, set up or fix remote access, diagnose intermittent connectivity, plan addressing or DNS, or assess whether the network's trust assumptions still hold.
telephony-and-conferencing
Runs voice and meeting infrastructure — phone systems and numbers, emergency calling obligations, conference rooms and their AV, call recording and its retention consequences, and the porting that makes provider changes go badly. Use this to replace a phone system, fix rooms nobody can start a meeting in, meet…
business-continuity-and-resilience
Plans for operating through disruption — impact analysis, recovery objectives, continuity plans, and the exercises that prove they work. Use this to run a business impact analysis, set RTO and RPO, write or test a continuity plan, prepare for a supplier or site failure, or answer a customer's resilience questionnaire.