What problem does it solve? When you tweak an installed aos capability — rescheduling a job, changing a threshold, adjusting a tone — a hand-edit to the rendered files gets silently wiped out by the next upgrade. This Skill captures every per-user change into a MOD.md overlay file so your personalizations persist across every upgrade. ## Core Features & Use Cases - Change classification: Routes each request to the right place — updating an onboarding answer, rewriting an existing MOD statement, adding a new imperative statement, or handing upstream fixes to the contribute skill. - Overlay-first writes: Writes the MOD.md change before applying it to the pinned render, then refreshes recorded hashes with aos-cap rehash so verification stays clean. - Capture mode: When drift is detected (a hand-edited render), folds the existing on-disk change back into MOD.md so upgrades no longer drop it. - Use Case: You ask your agent to make the steward capability run at 22:00 instead of the default. The Skill records the new schedule in your MOD.md, applies it to the render, and confirms it will survive every future upgrade. ## Quick Start Ask your agent to change an installed capability's behavior, for example: make the steward run at 22:00 and record it so it survives upgrades.