Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/bybren-llc/safe-agentic-workflownpx agentmods add skills/bybren-llc/safe-agentic-workflow/vault-syncWrote 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/bybren-llc/safe-agentic-workflow/vault-sync)<a href="https://agentmods.dev/skills/bybren-llc/safe-agentic-workflow/vault-sync"><img src="https://agentmods.dev/badge/skills/bybren-llc/safe-agentic-workflow/vault-sync/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/bybren-llc/safe-agentic-workflow/vault-sync"><img src="https://agentmods.dev/badge/skills/bybren-llc/safe-agentic-workflow/vault-sync.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00059 | $0.01336 |
| Opus 5.5 | $0.00024 | $0.00534 |
| Sonnet 5.5 | $0.00012 | $0.00267 |
| Haiku 4.5 | $0.00006 | $0.00134 |
Grade A, and why
vault-sync 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vault Sync Skill
TEMPLATE: This skill uses
{{PLACEHOLDER}}tokens. Replace with your project values before use.
Purpose
Keep an OKF knowledge vault honest as the code evolves. The vault is a map of the system; this skill detects drift between map and territory, regenerates only the affected concepts, and records the sync.
When This Skill Applies
Invoke this skill when:
- A significant change merged — schema, public interfaces, CI workflows, agent or skill config
- A staleness review is due (the
stale-conceptsBase is the queue) - The user asks to sync, refresh, or update the knowledge vault
- A concept is suspected of being wrong
Key Files
| Path | Role |
|---|---|
<vault>/_meta/vault-config.json |
Machine-readable constitution — types, tags, frontmatter contract |
<vault>/_meta/CONVENTIONS.md |
The human-readable rules |
<vault>/_meta/manifest.json |
ID registry, reverse index, and baseline_sha drift watermark |
<vault>/_meta/templates/ |
Per-type skeletons |
<vault>/log.md |
Dated changelog |
knowledge-vault/scripts/validate-vault.mjs |
The gate |
Procedure
1. Detect drift
Read the baseline and diff it to HEAD across the watch-list — the source paths your concepts claim to describe. Configure this list for your project; the example below is illustrative.
BASELINE=$(node -e "console.log(require('./<vault>/_meta/manifest.json').baseline_sha)")
git diff --name-only "$BASELINE"..HEAD -- \
'src/**' 'lib/**' 'config/**' '.github/workflows/**' 'docs/**'
A concept is stale if and only if a changed path matches its resource or an entry in its
sources. Check the manifest first (it is the reverse index); grep concept frontmatter as backup.
This is file-level truth. Do not substitute a time-based heuristic — "older than N days" flags everything and teaches people to ignore the flag.
2. Detect inventory changes
Re-enumerate your source globs and diff against the manifest.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 133 lines · 59 tokens per session scan A a710906b9469
vault-sync is a skill published in the GitHub repository bybren-llc/safe-agentic-workflow (425 stars, last pushed 3mo ago), licensed MIT. It adds 59 tokens to every session and 1,336 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-30.
Other skills, from other repositories
consistency-check
Scan GDDs against the entity registry for cross-document conflicts. Grep-first approach targets conflicting sections, different stats.
bug-report
Structured bug report from a description, or analyze code for potential bugs. Reproduction steps, severity.
hotfix
Emergency fix bypassing normal sprint process — hotfix branch, approvals tracked, backport verified, full audit trail.
bug-triage
Re-evaluate open bugs — priority vs severity, assign to sprints, surface systemic trends. Run when the count grows.
test-flakiness
Find flaky tests from CI logs — aggregates pass rates, spots intermittent failures, recommends quarantine. After multiple runs.
04-audit
Audit a codebase read-only across seven quality pillars into one ranked report. Use when the user wants to assess, health-check, or audit a codebase or one pillar. Not for fixing findings, reviewing a change, or checking a feature works.