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-groom/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-groom)<a href="https://agentmods.dev/skills/pass-agent/loomkin/vault-groom"><img src="https://agentmods.dev/badge/skills/pass-agent/loomkin/vault-groom/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/pass-agent/loomkin/vault-groom"><img src="https://agentmods.dev/badge/skills/pass-agent/loomkin/vault-groom.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.00019 | $0.00580 |
| Opus 5 | $0.00010 | $0.00290 |
| Sonnet 5 | $0.00004 | $0.00116 |
| Haiku 4.5 | $0.00002 | $0.00058 |
Grade A, and why
vault-groom 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 9d 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
Run a health check on the knowledge base and fix issues.
Team Mode (Large Vaults)
For large vaults (500+ entries), spawn a team to parallelize grooming:
team_spawn(
team_name: "vault-grooming",
purpose: "Audit, archive, and fix issues across a large vault",
roles: [
%{name: "vault-auditor", role: "researcher"},
%{name: "vault-archiver", role: "coder"},
%{name: "vault-fixer", role: "coder"}
]
)
Team roles:
- vault-auditor: Runs
vault_audit(scope: "full")and catalogs all issues. Shares the report with archiver and fixer. - vault-archiver: Processes completed task archival (
vault_kanban(action: "archive")), archives old checkins, and moves stale entries. - vault-fixer: Applies approved metadata fixes, corrects frontmatter, resolves structural issues.
For smaller vaults, skip team mode and process single-agent.
Audit
vault_audit(scope: "full") — get the full quality report.
Check Task Board
vault_kanban(action: "list", filter_column: "done") — find completed tasks ready for archive.
vault_kanban(action: "list", filter_column: "in_progress") — check for stale items (no activity in 7+ days).
Check Temporal Entries
vault_list(entry_type: "checkin") — find checkins older than 30 days for archiving.
Present Findings
Format as a structured report:
- Task issues (missing metadata, stale items)
- Completed tasks ready to archive
- Old checkins ready to archive
- Quality issues from vault_audit
- OKR/milestone status inconsistencies
Interactive Fix
Use ask_user to confirm each category of fix:
- "Archive these X completed tasks?"
- "Archive these Y old checkins?"
- "Fix these Z metadata issues?"
Apply Fixes
- Archive tasks:
vault_kanban(action: "archive") - Archive checkins:
vault_update_entry(status: "archived")for each - Fix metadata:
vault_update_entry(frontmatter_updates: "...")for each
Refresh
vault_dashboard(dashboard_type: "index") after all fixes.
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.
- 9d ago First seen · 80 lines · 19 tokens per session scan A 25743187bb4b
vault-groom is a skill published in the GitHub repository pass-agent/loomkin (179 stars, last pushed 3mo ago), licensed MIT. It adds 19 tokens to every session and 580 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-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…
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.
pause
Pause Mem0 memory capture on this machine. Use when the user wants to stop memories being recorded, for example for private work or experiments.
mine
Mine a project or conversation into your MemPalace — extract and store memories for later retrieval.