Borrowing it
Nothing to install: this file belongs to pass-agent/loomkin. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/pass-agent/loomkin/main/.agents/skills/vault-dashboard/SKILL.mdgit clone --depth 1 https://github.com/pass-agent/loomkinWrote 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/pass-agent/loomkin/vault-dashboard)<a href="https://agentmods.dev/skills/pass-agent/loomkin/vault-dashboard"><img src="https://agentmods.dev/badge/skills/pass-agent/loomkin/vault-dashboard.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.00010 | $0.00193 |
| Opus 5 | $0.00005 | $0.00097 |
| Sonnet 5 | $0.00002 | $0.00039 |
| Haiku 4.5 | $0.00001 | $0.00019 |
Grade A, and why
vault-dashboard 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 8d 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
Refresh the main dashboard entry with current state.
Index Dashboard
vault_dashboard(dashboard_type: "index")— get full dashboard data- Search for the current Index entry:
vault_search(query: "Index", entry_type: "topic") - If it exists,
vault_update_entry(path: "Index.md", content: "{formatted dashboard}")— rewrite with fresh data - If it doesn't exist, create it as a topic entry
Updates Hub
vault_dashboard(dashboard_type: "updates_hub")— get checkin summary- Update or create the updates index entry
Report
Confirm which dashboards were refreshed and any notable changes (new completions, at-risk items, etc.).
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.
- 8d ago First seen · 27 lines · 10 tokens per session scan A 3710180bbc5e
vault-dashboard is a skill published in the GitHub repository pass-agent/loomkin (179 stars, last pushed 3mo ago), licensed MIT. It adds 10 tokens to every session and 193 once invoked, about $0.0001 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
elixir
Use when writing or refactoring Elixir/OTP on the BEAM — GenServers, supervision trees and restart strategies, pattern matching, mix projects and releases — or when processes misbehave (restart loops, mailbox growth, call timeouts). NOT a Phoenix web app, LiveView, Ecto or channels (that is phoenix).
phoenix
Use when building an Elixir web app with Phoenix — contexts, Ecto schemas, changesets and migrations, LiveView, channels and PubSub, the generators, and the boundary between domain logic and the web layer. Covers the classic LiveView over-rendering and Ecto N+1 traps. NOT pure OTP work with no web or Ecto layer …
mem0-tour
Browses all stored memories grouped by category with full content display. Use when reviewing all project memories, exploring stored knowledge, onboarding to a project, or getting an overview of captured decisions, conventions, and learnings.
mem0-vercel-ai-sdk
Mem0 provider for Vercel AI SDK (@mem0/vercel-ai-provider). TRIGGER when: user mentions "vercel ai sdk", "@mem0/vercel-ai-provider", "createMem0", "retrieveMemories", "addMemories", "getMemories", "searchMemories", "mem0 vercel", "AI SDK provider", "AI SDK memory", or is using generateText/streamText with mem0. Also…
peek
Searches memories and displays compact one-liner results, or looks up a specific memory by ID. Use for quick memory lookups, checking if a decision was recorded, resolving [mem0:id] citations, or browsing memories without full category detail.
mine
Mine a project or conversation into your MemPalace — extract and store memories for later retrieval.