pv-migrate is a command-line tool and kubectl plugin that moves or backs up data stored in Kubernetes PersistentVolumeClaims, which are Kubernetes objects connected to persistent storage. It is for operators who need to transfer claim data between namespaces, clusters, or supported bucket-storage systems. Catalogue add-ons help coding agents operate the tool.
Borrowing it
Nothing to install: this file belongs to utkuozdemir/pv-migrate. 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/utkuozdemir/pv-migrate/main/AGENTS.mdgit clone --depth 1 https://github.com/utkuozdemir/pv-migrateWrote 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/instructions/utkuozdemir/pv-migrate/agents-md)<a href="https://agentmods.dev/instructions/utkuozdemir/pv-migrate/agents-md"><img src="https://agentmods.dev/badge/instructions/utkuozdemir/pv-migrate/agents-md.svg" alt="Measured on agentmods" 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.06476 | $0.06476 |
| Opus 5 | $0.03238 | $0.03238 |
| Sonnet 5 | $0.01295 | $0.01295 |
| Haiku 4.5 | $0.00648 | $0.00648 |
Grade A, and why
pv-migrate AGENTS.md 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 today.
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 — 281 lines — stays where its author put it; the contents beside it link to each section on GitHub.
pv-migrate — agent guide
This is the project's knowledge base for humans and agents working in this repository. Maintain it as you go: whenever you learn something durable about how this repo works, add it here. It is not append-only, so fix or delete anything that becomes wrong or outdated.
Keep it timeless. Two rules keep it from rotting: prefer pointers over copies, and prefer invariants over inventories. Never restate a flag list, a strategy table, a chart value, a file count, a version number or the current state of some in-flight work. Those live in the code and the docs, they change constantly, and a stale copy here is worse than no copy. What belongs here is the map, and the reasoning that is not written down anywhere else.
CLAUDE.md, GEMINI.md and .github/copilot-instructions.md point at this file, so this is the one place to edit.
The Copilot file additionally inlines a few of the rules below, because its consumer injects that file verbatim instead of following the pointer; keep those copies in sync.
Keep one sentence per line, and the first line as the single top-level heading.
What this repo is
A CLI and kubectl plugin that moves the contents of a Kubernetes PersistentVolumeClaim.
The premise is that a PVC is two things: an API object, which is trivial to recreate, and data in a storage backend, which is not. Everything here exists to move the second one, and it does that by running someone else's proven data mover inside the cluster rather than reimplementing one. There are two workflows: PVC to PVC directly over rsync, and PVC to and from bucket storage over rclone.
The tool itself is a one-shot client that owns no state. It renders an embedded Helm chart, waits, and uninstalls. That shape is the reason for most of what follows: everything it needs to say to the cluster has to survive being written into chart values, and everything it learns back it learns by reading pod logs.
README.md says what the project is for; docs/ carries the user-facing reference.
docs/security-model.md says what the tool promises security-wise and where the trust boundaries are, and docs/roadmap.md says what is planned and what is deliberately not.
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.
- today Changed · +9 lines · +378 tokens per session 413dd85a46d1
- 2d ago Changed · +25 lines · +892 tokens per session f48a8c408f36
- 7d ago First seen · 247 lines · 5,206 tokens per session scan A cdaf866d23a4
pv-migrate AGENTS.md is an instructions file published in the GitHub repository utkuozdemir/pv-migrate (2,402 stars, last pushed today), licensed Apache-2.0. It adds 6,476 tokens to every session, about $0.0324 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 instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.