My personal Codex instructions, skills, and optional MCP configuration, kept in Git so I can review changes and restore the same setup on another machine. Others can use the collection or fork it for their own preferences.
Codex reads the installation guide, asks what you want, and performs the setup using its available tools. AgentPack has no CLI, installation script, package build, or plugin distribution.
You need a working Codex CLI and Git. Paste this into Codex:
Install https://github.com/boman-ng/agentpack from its master branch.
Read README.md and INSTALL.md first, then inspect my Codex setup.
Ask which local skills and complete third-party suites I want, along with
instructions and optional MCP. Show the exact content that will
be replaced or removed. After I confirm that scope, complete the backup,
installation, and verification without asking again about settled choices.
Report the installed revisions, verification results, and backup location.
The recommended starting point is the global instructions and cleanup. Third-party skills and AnySearch are optional. Only user-level Codex configuration is supported.
Selected components are taken over: selected skill and MCP collections are replaced with your confirmed selection, including removal of entries not in that selection. Skipped components stay unchanged. The shared ~/.agents/skills directory may also be used by other clients, so replacing that collection affects their shared skills too. Codex shows the actual targets and archives existing content before making changes. See INSTALL.md for the boundaries and recovery instructions.
| Content | Purpose |
|---|---|
| Global instructions | Personal working preferences for Codex |
| cleanup | Review and simplify code or agent instructions |
| ui-translate | Turn rough UI and motion ideas into frontend terms and developer descriptions |
| Skill catalog and sources | Local skills and complete optional upstream suites at recorded Git commits |
| AnySearch configuration | Optional anonymous remote search MCP |
Browse skills by task: engineering maintenance, interface design and development, research and academic writing, or browser and app automation. Categories help you find capabilities; select local skills individually and third-party suites as complete units. Opening a category does not select everything in it.
Third-party skills are fetched from their recorded sources when their suite is selected; they are not bundled here. Their required tools are separate: installing the agent-browser skill, for example, does not install its executable or a browser. Motion's connected tools need separate MCP setup and may require account or paid access. SOURCES.md records prerequisites and licenses. Academic Research Suite has a non-commercial license.
Ask Codex to read INSTALL.md, inspect your installation record, and update the same components from the current master commit. To reproduce a previous setup, provide the recorded AgentPack commit instead. Updating AgentPack uses the upstream commits in that revision's source list; upgrading an upstream dependency means reviewing and changing that list.
Edit personal instructions and local skills in your checkout or fork, then commit and push them. Installed files are copies; direct edits to a selected installation target will be overwritten on the next update.
For recovery, ask Codex to inspect the recorded backup and restore the affected targets. There is no automatic background updater or state-driven uninstall. Existing installation backups remain available until you choose to remove them.
The root AGENTS.md describes repository maintenance; it is not the global instruction payload. Keep content, source revisions, and links valid. Installation changes are exercised in disposable directories, never against the maintainer's real Codex configuration.
Earlier software releases remain identifiable by their Git tags. Their installation commands, build workflows, and state formats do not apply to this content-based setup.
Original material is MIT-licensed. See third-party attribution and the security and recovery boundaries.