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 agentmods add skills/ondrasek/cc-plugins/vault-updatenpx skills add ondrasek/cc-plugins --skill vault-updategit clone --depth 1 https://github.com/ondrasek/cc-pluginsWhat 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 | $0.00055 | $0.00554 |
| Opus 5 | $0.00028 | $0.00277 |
| Sonnet 5 | $0.00011 | $0.00111 |
| Haiku 4.5 | $0.00006 | $0.00055 |
Grade A, and why
vault-update 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 2d 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vault Update
Context Files
skills/shared/references/methodology-framework.md— shared principles, hook architecture, exit codesskills/vault-setup/references/methodology.md— current methodology (latest version)skills/vault-setup/templates/— current templatesskills/vault-setup/references/workflow-catalog.md— current GitHub workflow categories
Workflow
Follow the 6-step update workflow below. Vault-specific: preserve existing .gitignore customizations, hook customizations, workflow customizations, and spelling dictionary entries.
1. Detect Current State
Same analysis as the audit skill — inventory existing tools, hooks, CI, and configuration. Identify which methodology version was previously applied by reading existing hook scripts and config.
2. Identify Differences
Compare current state against the latest methodology:
- New tools recommended for unfilled roles
- Updated configurations (new frontmatter fields, updated spelling dictionaries)
- New templates (hook script improvements, workflow additions from workflow-catalog.md)
- Changed thresholds or adaptation rules
- New workflow catalog entries not yet adopted
3. Present Update Plan
Show the user what would change before making any modifications. Wait for approval.
4. Apply Updates
Apply approved changes one dimension at a time:
- Merge config changes (preserve existing
.gitignoreentries, custom spelling words, frontmatter field customizations) - Update hook scripts (preserve custom check additions or threshold overrides)
- Update CI workflows (preserve custom job additions or workflow triggers)
- Update GitHub Actions workflows from workflow catalog if new categories apply
- Install new tools if needed
5. Verify
Run the quality gate to confirm no breakage. Distinguish methodology improvements from regressions.
6. Report
Summarize updates applied and any manual steps remaining.
Important Notes
- Always show the update plan before making changes
- Preserve vault-specific customizations (custom frontmatter schemas, extra
.gitignoreentries, spelling dictionary additions, workflow customizations) - If a vault has deliberately disabled a dimension, do not re-enable it
- Update one dimension at a time to make changes reviewable
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.
- 2d ago First seen · 62 lines · 55 tokens per session scan A 1e19efef645f
vault-update is a skill published in the GitHub repository ondrasek/cc-plugins (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 55 tokens to every session and 554 once invoked, about $0.0003 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
hr-onboarding
A new-hire onboarding plan as a single page — first week schedule, buddy + manager intro, learning track, equipment checklist, and "you're set when…" outcomes. Use when the brief mentions "onboarding", "new hire", "first week plan", or "入职".
lark-im
飞书即时通讯：收发消息和管理群聊。发送和回复消息、搜索聊天记录、管理群聊成员、上传下载图片和文件、管理表情回复、发送应用内/短信/电话加急、发送和处理交互卡片（Interactive Card）、监听卡片按钮回调（card.action.trigger）。当用户需要发消息、查看或搜索聊天记录、下载聊天中的文件、查看群成员、搜索群、创建群聊或话题群、管理标记数据、管理 Feed 置顶（添加/移除/查询置顶会话）、管理标签数据、处理卡片回调时使用。.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
reflect
Review recent work, find repeated workflow patterns, and suggest reusable skills, agents, commands, config changes, or playbooks. Use when the user asks to learn from past sessions, improve recurring workflows, or identify what should be turned into reusable agent instructions.
mochi-remind
Handle due reminders — notify the user with natural language and mark them done.
organize-threads
猫猫辅助整理未分类 thread，分析标题和元数据，建议合适的标签。 Use when: 用户说"帮我整理"、"分类 thread"、点击整理按钮。 Not for: 删除/编辑标签本身。 Output: 按 thread 的标签建议列表。.