Skip to content

Ownership model

Agents Pack keeps ownership explicit so you know which content is official, which is yours to edit, and which files are generated outputs.

Official components use the reserved ap- prefix. They come from the content pack (registry or local pack) and may be replaced during an official update.

Examples: ap-debug, ap-frontend-design, ap-code-reviewer, ap-manage-agents-pack.

User-created names cannot use the ap- prefix.

User-owned skills and subagents have one canonical source. Edit that source, then run sync to regenerate Claude Code, Codex, and Cursor copies.

Scope Canonical source
Repository .agents-pack/user/
Global ~/.agents-pack/user/

Example skill path after agents-pack create skill deploy-app:

.agents-pack/user/skills/deploy-app/SKILL.md

Subagents use provider-neutral agent.toml and instructions.md under the user catalog. Agents Pack renders each provider’s native definition from that source.

User-owned components appear in agents-pack list with a user-owned label.

Provider-native files under Claude, Codex, and Cursor paths are outputs, not the source of truth. Direct edits to those copies are treated as drift and block synchronization or other mutating operations.

Make changes under .agents-pack/user/ or ~/.agents-pack/user/, then run:

Terminal window
agents-pack sync --dry-run
agents-pack sync --yes
agents-pack status

Codex instructions live in a marked managed block inside AGENTS.md. Text outside that block remains yours. A malformed or conflicting block stops the operation — Agents Pack will not silently merge or overwrite drifted content.

Operation Official pack content User canonical source
Update May change Preserved
Rollback Restored from cache Preserved
Eject Generated copies and lifecycle state removed Preserved under .agents-pack/user/ or ~/.agents-pack/user/