Fork and customize
Fork and customize
Section titled “Fork and customize”If an official skill or subagent is close to what you want but should become yours, fork it. Do not edit the generated official copy in place — that is drift.
Fork an official component
Section titled “Fork an official component”agents-pack fork ap-debug --name my-debug --dry-runagents-pack fork ap-debug --name my-debug --yesForking:
- copies the exact installed official source;
- gives the copy your new user-owned name;
- records it as a separate user-owned component; and
- renders the copy for every selected agent.
The new name cannot use the reserved ap- prefix.
Only official skills and subagents can be forked. Official instruction components cannot be forked — put repository-specific instruction additions outside Agents Pack’s managed block or in a user-owned skill.
After the fork
Section titled “After the fork”Future official updates do not overwrite your copy. The original official component stays installed and continues to receive updates.
Edit the canonical user-owned source under .agents-pack/user/ or ~/.agents-pack/user/, then run agents-pack sync when needed. See Create user components and Ownership.
Via coding agent
Section titled “Via coding agent”Fork ap-debug into a user-owned skill named my-debug, then show me whichcanonical file I should customize.Remove the original (optional)
Section titled “Remove the original (optional)”If you no longer want the official component, remove it separately after the fork:
agents-pack remove ap-debug --dry-runagents-pack remove ap-debug --yesRequired official components cannot be removed.