What is volsync-carveouts?

A set of guidance for VolSync, a Kubernetes backup and restore tool, covering a small set of persistent volumes and their replication objects. It describes how snapshots and restore destinations are created and retained.

Use it before changing VolSync components, replication sources or destinations, restore procedures, or the listed Paperless and Syncthing storage overlays.

It prevents adding VolSync to unsupported applications and explains why a restore can leave a healthy-looking but empty volume. It also avoids triggering restores through edits that create lasting configuration drift.

How Aviator-Coding/home-ops configures Claude Code and Codex

Reuse

Borrowing it

Nothing to install: this file belongs to Aviator-Coding/home-ops. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/Aviator-Coding/home-ops/main/.agents/skills/volsync-carveouts/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/Aviator-Coding/home-ops

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/aviator-coding/home-ops/volsync-carveouts/github.svg)](https://agentmods.dev/skills/aviator-coding/home-ops/volsync-carveouts)

Your own site

<a href="https://agentmods.dev/skills/aviator-coding/home-ops/volsync-carveouts"><img src="https://agentmods.dev/badge/skills/aviator-coding/home-ops/volsync-carveouts/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/aviator-coding/home-ops/volsync-carveouts"><img src="https://agentmods.dev/badge/skills/aviator-coding/home-ops/volsync-carveouts.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 60 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,267 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00060	$0.01267
Opus 5.5	$0.00024	$0.00507
Sonnet 5.5	$0.00012	$0.00253
Haiku 4.5	$0.00006	$0.00127

Measured 23d ago against content hash 99e0f7179c34, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

volsync-carveouts 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 23d 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.

.agents/skills/volsync-carveouts/SKILL.md · 84 lines

How it starts

The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.

VolSync carve-outs

VolSync is the second engine on three claims, and nowhere else. Do not add components/volsync to a new app. kopiur is the norm (skill kopiur-backups). Delete this skill when those three claims leave VolSync.

The three: selfhosted/paperless-ngx (permanent), paperless-ngx-media, syncthing-data. Each still gets three ReplicationSource objects (ceph, minio, r2) and one ReplicationDestination.

Tripwires

${APP}-dst.status.latestImage is frozen at first apply. The destination runs trigger.manual: restore-once once, then ssa: IfNotPresent stops Flux from reconciling it. pvc.yaml populates from that VolumeSnapshot, not from the restic repository. If the first run logged No eligible snapshots found, latestImage is an empty volume forever. Deleting only the PVC restores nothing while Bound, Running and Ready all stay green. Delete the ReplicationDestination together with the PVC. Read status.latestMoverStatus.logs and status.lastSyncTime before trusting dataSourceRef. restore-procedures.md
Never patch <app>-dst to trigger a restore. The manual edit persists forever and can drift spec.restic.repository. Create a new, uniquely named scratch ReplicationDestination plus PVC against the existing read-only credential Secret. Live restore into the app claim is just kube restore <namespace> <app>, which derives <app>-manual and does not patch <app>-dst.
A restore relaxes every mode by one group-write bit (644 to 664, 600 to 660, 755 to 775). The mover stages the destination writable, so kubelet's fsGroup walk runs before restic writes. Ownership is unchanged. kopiur restores keep the original modes. Do not use a VolSync restore to reproduce a permissions bug.
Deleting a ReplicationSource never touches the restic repository. That is why retirement is survivable, and why a retention policy cannot empty a frozen repository.
paperless-ngx still has ${VOLSYNC_CLAIM:-*app}. That alias is armed on purpose. Removing VOLSYNC_CLAIM makes flate fail the Kustomization. syncthing and syncthing-data are different claims in one overlay file.
Retired-repository expiry is NOT IN FORCE. Nothing in Git applies it. Rook's ObjectBucketClaim controller has no update path, so bucketLifecycle on the volsync bucket is a silent no-op. Match a repository by the exact path segment <name>/. volsync/syncthing is a string prefix of volsync/syncthing-data. retired-repo-expiry.md
A uid mismatch does not mean the restic backup is incomplete. Writable staging lets fsGroup add group-read before restic opens the file. Measure with a restore, or with find <mount> -type f ! -readable as the mover uid. kopiur fails closed on the same mismatch.
One component include is one volume. A second PVC is a second Kustomization with path: ./kubernetes/components/volsync/backup and APP set to the claim name. multi-volume.md
VOLSYNC_CACHE_CAPACITY is 20-50% of the PVC for large claims and 50-100% for small ones. Cache is a mover scratch volume, not the kopiur restore-cache cliff.

Read the full file on GitHub · 84 lines

Files

What ships with it

6 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.

Changes

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.

23d ago Changed 99e0f7179c34
25d ago First seen · 84 lines · 60 tokens per session scan A 6c9e4074c9f6

Subscribe to this mod's changes

volsync-carveouts is a skill published in the GitHub repository Aviator-Coding/home-ops (3 stars, last pushed today), licensed MIT. It adds 60 tokens to every session and 1,267 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-09-29.

DevOps and cloud

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

home-ops: Skill for Claude Code