MCPVault is a local Model Context Protocol server that lets compatible AI clients read, search, and edit notes stored in an Obsidian vault. It is for users who want coding agents and other supported clients to work with their vault while restricting file access to its configured root. The catalogue entries provide add-ons for using MCPVault with AI coding agents.
Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/bitbonsai/mcpvault/triage)<a href="https://agentmods.dev/skills/bitbonsai/mcpvault/triage"><img src="https://agentmods.dev/badge/skills/bitbonsai/mcpvault/triage.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.1 | $0.00108 | $0.02189 |
| Opus 5 | $0.00054 | $0.01094 |
| Sonnet 5 | $0.00022 | $0.00438 |
| Haiku 4.5 | $0.00011 | $0.00219 |
Grade A, and why
triage 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 6d 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 — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Triage Skill
A self-resuming morning loop. One run = gather → load state → triage →
fan-out fix → persist → spill. Everything personal (state, inbox, runs,
voice) lives under .triage/, which is gitignored. This skill file and the
scripts are committed; the data never leaves the machine.
Preconditions
ghauthenticated (gh auth status). All issue/PR/CI reads and writes go through it..triage/exists. If missing, runscripts/triage/bootstrap.shfirst, it scaffoldsstate.json,inbox.md,runs/, and bootstrapsvoice.mdfrom past comments.- Clean working tree on
main. The loop only mutates.triage/on the base checkout; all code changes happen in worktrees.
The loop
1. Gather (read-only)
Collect yesterday's signals. Compute the window from state.json.last_run
(fall back to 24h if absent).
# CI failures since last run
gh run list --status failure --created ">=$SINCE" --json databaseId,name,headSha,conclusion,url
# for each, pull the failing step log
gh run view <id> --log-failed
# open issues
gh issue list --state open --json number,title,labels,updatedAt,author,url
# recent commits
git log --since="$SINCE" --pretty='%h %s %an'
Then scan for open commitments, promises the maintainer made in a comment that have not shipped. NOT time-windowed: check every open issue/PR.
# threads bitbonsai commented on, still open
gh search issues "commenter:bitbonsai repo:bitbonsai/mcpvault state:open" --json number
# per thread, pull bitbonsai's comments to inspect for a promise
gh issue view <n> --json comments \
--jq '.comments[] | select(.author.login=="bitbonsai") | .body'
A commitment is language that promised an action: "I'll fix this", "will add",
"shipping next release", "on it", "going to look", etc. It is broken/open if the
thread is still open and no merged PR resolved it. See finding-rules.md.
2. Load state
Read .triage/state.json. Build a map of known findings by id. The id is
a stable hash of source + signature (see resources/state-schema.md), so
the same failing test or issue always maps to the same finding across runs.
What ships with it
3 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.
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.
- 6d ago First seen · 206 lines · 108 tokens per session scan A ffc0cc6f7a09
triage is a skill published in the GitHub repository bitbonsai/mcpvault (1,647 stars, last pushed 5d ago), licensed MIT. It adds 108 tokens to every session and 2,189 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-30.
Other skills, from other repositories
import-prom-rule
Bulk import of a Prometheus alert rule YAML file (create a whole set of rules at once). Dedicated to handling a remote URL or local YAML text, automatically parsing the three formats groups / a plain rules array / a single rule. ⚠️ Do not use this skill for single-rule creation — when the user describes a single alert…
azsdk-common-pipeline-analysis
Analyze Azure SDK CI/CD pipeline failures into a structured diagnosis, and define the required output format. Load this skill before calling azsdkanalyzepipeline, which returns raw failure data that this skill interprets and formats. USE FOR: "pipeline failed", "build failure", "CI check failing", "tests failing in…
configure-env-variables
Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…
desktop-principles
Desktop-specific UX principles - hover states, pointer precision, keyboard shortcuts, multi-window, focus management. Covers macOS, Windows, Linux, web desktop.
atmos-cache
Atmos caching: CI cache configuration and commands, GitHub Actions cache integration, Terraform registry cache mirror/list/prune/stats/trust, and cache modernization guidance.
atmos-profiles
Atmos profiles: profile directories, --profile and ATMOSPROFILE activation, profile merge behavior, environment switching, and routing profile-specific auth/toolchain/config overrides.