Agent Full Backup

Agent Full Backup turns a scattered agent setup into one verified archive: every skill, every knowledge or memory file, and every agent configuration file, copied byte for byte into a single zip organized into Skills, Knowledge, and Agents folders, with a checksum manifest and a restore protocol alongside.

What it does

• Maps your setup first. Intake identifies your skills root, your knowledge or memory root, and your agents folder when one exists, with the mapping confirmed before anything is copied.
• Inventories everything. A recursive walk records every file with its path and size, including hidden files and dotfiles where agent setups keep their state.
• Screens for secrets. Likely credentials are flagged by path and pattern only, never by value, and you decide include or exclude per file with the decision recorded in the manifest.
• Copies byte for byte. Zero transformation: no reformatting, no re-encoding, no line-ending conversion, so the archive matches the source exactly.
• Builds the manifest. BACKUP-MANIFEST.md records the date, the source roots, per-folder counts and bytes, and an MD5 checksum for every file.
• Verifies before delivery. Archive integrity, count match, checksum re-verification of every extracted file, totals reconciliation, and byte-fidelity checks must all pass before the archive is handed over.
• Restores safely. A restore protocol extracts to a staging area, verifies against the manifest, and merges into a live setup with conflicts surfaced for your decision.

How it works

• The agent confirms your three roots and the destination, then inventories each root recursively and reports counts and standout file types before copying.
• Files are staged into Skills/, Knowledge/, and Agents/ preserving relative paths. The Agents folder is included when agent files exist, and its absence is stated plainly in the manifest when they do not.
• The manifest is written at the archive root, the tree is zipped with the date in the name, and a six-check verification pass runs on the archive itself.
• The delivery report carries the real numbers from the verification pass, and any check the environment cannot run is reported as unverified rather than assumed.

Why this beats prompting it yourself

A one-off prompt asks an agent to copy some folders, and the failure modes are predictable: the memory folder missed because it lives under a dotfile path, purchased skills skipped because a root was guessed, line endings quietly converted so files no longer match their sources, credentials copied into a zip with no record of the decision, and no way to prove months later that the archive is complete and uncorrupted. The skill fixes each failure by structure: confirmed roots, a full inventory, a secrets screen with recorded decisions, a checksum for every file, and a verification pass that re-extracts the archive and compares every checksum before delivery. The backup runs entirely on your machine and uploads nothing.

Known limitations

Anything living purely in a cloud service stays out of scope; only files on the machine can be archived. The secrets screen is pattern-based and catches common credential shapes without claiming completeness. Binary and database files are carried as files with no content inspection beyond the screen. Verification depth depends on the commands your environment provides.