Borrowing it
Nothing to install: this file belongs to xcota/pos. 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/xcota/pos/main/.claude/skills/vault-scaffolder/SKILL.mdgit clone --depth 1 https://github.com/xcota/posWrote 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/xcota/pos/vault-scaffolder)<a href="https://agentmods.dev/skills/xcota/pos/vault-scaffolder"><img src="https://agentmods.dev/badge/skills/xcota/pos/vault-scaffolder/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/xcota/pos/vault-scaffolder"><img src="https://agentmods.dev/badge/skills/xcota/pos/vault-scaffolder.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 12 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 112 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Memory Poisoning · line 206 Skill attempts to fill the context window with filler content, displacing legitimate instructions and safety constraints. This can degrade agent performance or bypass safety boundaries.Fix: Implement context-window management that detects and rejects padding or stuffing attempts. Prioritize system instructions over user-injected content.
- medium Memory Poisoning · line 219 Skill attempts to fill the context window with filler content, displacing legitimate instructions and safety constraints. This can degrade agent performance or bypass safety boundaries.Fix: Implement context-window management that detects and rejects padding or stuffing attempts. Prioritize system instructions over user-injected content.
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.00029 | $0.05517 |
| Opus 5 | $0.00015 | $0.02759 |
| Sonnet 5 | $0.00006 | $0.01103 |
| Haiku 4.5 | $0.00003 | $0.00552 |
Grade A, and why
vault-scaffolder 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 10d 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 — 335 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/vault-scaffolder — Personalize the Personal OS (in-place)
Takes a completed svoboda profile.yaml (v3.2 schema) and personalizes the Personal OS in the current workspace. Overwrites the blank onboarding CLAUDE.md, writes context/identity.md, context/goals.md, the self-entity, and the operational layer, and appends profile-specific anti-patterns to the shipped corpus.
Assumes the engine is already present. Skills (.claude/skills/), templates (_templates/), context/scoring-gate.md, AND the shipped engine corpus — context/anti-patterns.md, anti-patterns-index.md, context/learned.md, learned-index.md, rules/*.md — all ship with the starter repo. The scaffolder personalizes content; it does NOT re-scaffold skills, templates, or the AP/L corpus. It NEVER regenerates anti-patterns.md or learned.md — it appends to them.
Reads the v3.2 nested schema directly (see contract below). It does not require the profiler to flatten anything.
Invocation
/vault-scaffolder {subject_id}
Input
- Required:
{subject_id}argument - Read
memory/svoboda/{subject_id}/profile.yaml - If missing → error:
"Run /svoboda-profiler {subject_id} first"
profile.yaml — schema contract (v3.2, must match svoboda-profiler)
This is the SAME canonical schema defined in svoboda-profiler/SKILL.md Phase 4. Read these exact keys. Nesting matters.
subject_id: str # kebab-case, == folder name
profile_version: str # top-level (e.g. "2.0")
synthesized: str # YYYY-MM-DD
identity: # NESTED map
name: str
age: int
role: str
languages: [str, ...] # languages[0] = primary
timezone: str # IANA tz
svoboda_scores: # NESTED map, 1-10 each (OBSERVED)
samorazvitie: int
vitalnost: int
okruzhenie: int
bogatstvo: int
otdyh: int
delo: int
aktivy: int
domains_active: [str, ...] # FLAT list
north_star: str # 1-2 sentences, verbatim into goals.md
style: direct|explanatory|mixed
cognitive_style: scanning|deep-dive|burst|gradual
triggers: [str, ...] # FLAT list, 3-5 items
blind_spots: [str, ...] # FLAT list
predictive_model: [{situation: str, behavior: str}, ...] # list of rows
tags: # NESTED map (NOT a flat list)
core_confirmed: [str, ...]
refined: [str, ...]
retired_from_baseline: [str, ...]
synthesis_constraint: str # optional free-text guardrail
# Optional / advisory (read if present, otherwise skip — do NOT fail):
score_divergence: [...]
granularity_coverage: {...}
cadence: {chronotype, reflection}
# plus v3.2 deep-layer fields (attachment, attribution, ...) — NOT consumed here.
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.
- 10d ago First seen · 335 lines · 29 tokens per session scan A 69a3b8d2ecad
vault-scaffolder is a skill published in the GitHub repository xcota/pos (40 stars, last pushed 1mo ago), licensed MIT. It adds 29 tokens to every session and 5,517 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
second-brain-climb
A guide for maintaining a long-term personal direction as a structured, evidence-based plan. It describes the desired destination, current position, gaps, possible routes, limits, evidence, and next actions.
ori-memory
Persistent agent memory with learning retrieval. Knowledge graph on markdown files — capture insights, decisions, research, and learnings during work, then retrieve them weeks or months later. Use when knowledge is too valuable to lose but too much to inject into every prompt.
day-log
Quick timestamped log entry — no conversation, just capture.
period-summary
Period summary (w/m/q/y) — reflect on the period, score it, close it out.
day-start
Day briefing — deliver context, capture what's happened, get moving.
start-jumbo-goal
Use when starting a Jumbo goal. Loads goal context, scope, and architectural constraints, then guides the agent through disciplined execution within defined boundaries.