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 fakechris/obsidian_vault_pipeline --skill claimgit clone --depth 1 https://github.com/fakechris/obsidian_vault_pipelineWrote 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/fakechris/obsidian_vault_pipeline/claim)<a href="https://agentmods.dev/skills/fakechris/obsidian_vault_pipeline/claim"><img src="https://agentmods.dev/badge/skills/fakechris/obsidian_vault_pipeline/claim/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/fakechris/obsidian_vault_pipeline/claim"><img src="https://agentmods.dev/badge/skills/fakechris/obsidian_vault_pipeline/claim.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.00039 | $0.00299 |
| Opus 5 | $0.00019 | $0.00150 |
| Sonnet 5 | $0.00008 | $0.00060 |
| Haiku 4.5 | $0.00004 | $0.00030 |
Grade A, and why
claim 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 3d 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
OVP Claim
Use the ovp2 MCP claim tool to load one durable claim’s full evidence closure: claim text, gate verdicts, and every citation resolved to verbatim quote, line, and source (title/sha/url).
When to use
- Auditing a
[claim:…]citation fromaskor a theme page - Resolving
ovp://claim/<key>or ack-…claim_key - Checking whether an answer’s receipt is real before trusting it
Arguments
| Arg | Required | Notes |
|---|---|---|
key |
yes | claim_key (preferred, stable), claim_id, or ovp://claim/<key> |
Behavior
- Call MCP
claimwith the key from the citation. - Present claim text, verdicts, and quote→source links clearly.
- If the key does not resolve, say so — do not invent evidence.
Notes
claim_keyvalues (ck-…) are deterministic and survive re-runs; safe to store in notes and answers.- Same payload as the
ovp://claim/<key>resource.
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.
- 3d ago First seen · 32 lines · 39 tokens per session scan A b4995fd6b50e
claim is a skill published in the GitHub repository fakechris/obsidian_vault_pipeline (163 stars, last pushed yesterday), licensed Apache-2.0. It adds 39 tokens to every session and 299 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-09-08.
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…