codex-keysmith

Why we included this project

Keeping a personal instruction file for Codex, whether it is a tuned system prompt, an agency-style ruleset, or a team house-style guide, is usually a fragile hand edit. This tool makes it repeatable and reviewable: it reads a Markdown instruction file, shows you exactly what will change in your Codex configuration, and writes only after you confirm, keeping a backup and an ownership manifest so you can roll back or uninstall cleanly. The hook isolation is the part that earns its keep in real use, since it suspends your existing hooks.json rather than letting an unverified instruction deployment quietly interact with the rest of your setup. If you standardize prompts across machines or iterate on instructions weekly, the selling point is that a failed or unwanted change stays recoverable instead of leaving your config in an unknown state. This is a command-line tool for managing prompts, not a model or assistant itself.