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 psenger/ai-agent-skills --skill vault-scribegit clone --depth 1 https://github.com/psenger/ai-agent-skillsWrote 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/psenger/ai-agent-skills/vault-scribe)<a href="https://agentmods.dev/skills/psenger/ai-agent-skills/vault-scribe"><img src="https://agentmods.dev/badge/skills/psenger/ai-agent-skills/vault-scribe/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/psenger/ai-agent-skills/vault-scribe"><img src="https://agentmods.dev/badge/skills/psenger/ai-agent-skills/vault-scribe.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.00095 | $0.02592 |
| Opus 5 | $0.00048 | $0.01296 |
| Sonnet 5 | $0.00019 | $0.00518 |
| Haiku 4.5 | $0.00010 | $0.00259 |
Grade A, and why
vault-scribe 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 10d 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 — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vault Scribe — Obsidian + GitHub Markdown Skill
Creates and edits Markdown that is GitHub-Flavored Markdown (GFM) first, with optional Obsidian-specific extensions when needed. Standard Markdown (headings, bold, italic, lists, quotes, code blocks, tables) is assumed knowledge.
Default rule: Use standard GFM syntax unless the user explicitly requests Obsidian-specific features or is working in an Obsidian-only context. Obsidian wikilinks (
[[Note]]) break on GitHub — always prefer standard Markdown links for cross-platform compatibility.
When invoked with an argument (e.g. /vault-scribe meeting), use $ARGUMENTS to determine the note type. If no argument is provided, infer the type from the source material or ask the user.
Workflow: Creating a Note
1. Analyse the Source Material
- Read the full transcript, notes, or brief carefully
- Identify the core topic, intended audience, and key concepts
- Note any implicit structure (e.g., problem → solution → examples)
- Extract any explicit examples, warnings, tips, or quotes worth preserving
2. Generate YAML Front Matter
Reference: See
references/FRONT-MATTER.mdfor the complete schema definitions, all enum values, and type-specific required fields.
First, determine the note type based on what the user is creating:
| If the user wants… | Set type to |
|---|---|
| A guide, reference doc, or knowledge article | article |
| A step-by-step instructional guide or procedure | how-to |
| Architecture docs, RFCs, design docs, system specs | technical |
| An investigation with multiple sources | deep-research |
| A versioned plan or strategy document | strategy |
| Meeting notes, 1:1s, standups, retrospectives | meeting |
| Brainstorming, ideation, or exploratory thinking (solo or group) | brainstorming |
[!TIP] Brainstorming is its own note type. It works for group sessions (add
attendeesandmeeting_date) and solo AI ideation (omit them). Addsourceswhen the brainstorm draws on external references.
What ships with it
9 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- examples/article-example.md 1.7 KB
- examples/how-to-example.md 3.5 KB
- examples/meeting-brainstorm-example.md 1.4 KB
- examples/technical-example.md 4.1 KB
- examples/transcript-example.md 2.3 KB
- references/CALLOUTS.md 2.6 KB
- references/EMBEDS.md 1.9 KB
- references/FRONT-MATTER.md 15 KB
- references/MARKDOWN-SYNTAX.md 4.9 KB
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.
- 10d ago First seen · 223 lines · 95 tokens per session scan A 30a335091715
vault-scribe is a skill published in the GitHub repository psenger/ai-agent-skills (10 stars, last pushed 3mo ago), licensed MIT. It adds 95 tokens to every session and 2,592 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
article-writing
Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…
printing-press-import
Bring a published CLI from the public library into the internal library so it's identical to a freshly-generated copy — module path reverted, manuscripts placed alongside, ready for /printing-press-polish or /printing-press-emboss. Use when the public library has a CLI you don't have locally, or to recover from a…
rework-rate
Measure and interpret PR rework rate — the emerging 5th DORA metric.
taiyi-ui-design
A design-planning guide for describing how an application's user interface should look and behave. It produces a UI-DESIGN.md document covering layouts, components, interactions, accessibility, and error states.
ln-62-repository-publisher
Commits, pushes, and remotely verifies authorized repository changes. Not for releases, package publication, or announcements.