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 ondrasek/cc-plugins --skill vault-updategit clone --depth 1 https://github.com/ondrasek/cc-pluginsWrote 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/ondrasek/cc-plugins/vault-update)<a href="https://agentmods.dev/skills/ondrasek/cc-plugins/vault-update"><img src="https://agentmods.dev/badge/skills/ondrasek/cc-plugins/vault-update/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/ondrasek/cc-plugins/vault-update"><img src="https://agentmods.dev/badge/skills/ondrasek/cc-plugins/vault-update.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.00055 | $0.00554 |
| Opus 5.5 | $0.00022 | $0.00222 |
| Sonnet 5.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 1mo 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.
- 1mo 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 5mo ago), licensed Apache-2.0. It adds 55 tokens to every session and 554 once invoked, about $0.0002 per session on Opus 5.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
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
agentmail
Use your assigned AgentMail inbox to read email tasks, explicitly send or reply, and check delivery. Provided automatically by your inbox assignment.
rowboat-spaces
How to work as a member of Rowboat Spaces, the team chat where people and agents work together. Load it once per session, before acting on any request that reaches you from Rowboat; it covers your setup, mentions and hand-offs, the tools, and files.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…