Hubwriter/update agents path (#59941)

Author: hubwriter

content/copilot/how-tos/copilot-cli/customize-copilot/create-custom-agents-for-cli.md

@@ -31,7 +31,7 @@ Each {% data variables.copilot.copilot_custom_agent_short %} is defined by a Mar
 1. Choose between the options to create the {% data variables.copilot.copilot_custom_agent_short %} in the repository or in your home directory:
 
    * **Project** (`.github/agents/`)
-   * **User** (`~/.config/copilot/agents/`)
+   * **User** (`~/.copilot/agents/`)
 
    > [!NOTE]
    > If you have {% data variables.copilot.custom_agents_short %} with the same name in both locations, the one in your home directory will be used, rather than the one in the repository.
@@ -136,4 +136,5 @@ Each {% data variables.copilot.copilot_custom_agent_short %} is defined by a Mar
 
 * [AUTOTITLE](/copilot/concepts/agents/copilot-cli/comparing-cli-features)
 * [AUTOTITLE](/copilot/reference/custom-agents-configuration)
+* [AUTOTITLE](/copilot/reference/cli-command-reference#custom-agents-reference)
 * [AUTOTITLE](/copilot/tutorials/customization-library/custom-agents)—a curated collection of examples

content/copilot/reference/custom-agents-configuration.md

@@ -153,3 +153,9 @@ The `tools` list filters the set of tools that are made available to the agent -
 ### MCP server configurations
 
 For MCP server configurations, there is a specific processing order that ensures proper override behavior: out-of-the-box MCP configurations (like the {% data variables.product.github %} MCP) are processed first, followed by the {% data variables.copilot.copilot_custom_agent_short %} MCP configuration, and finally MCP configurations specified through repository settings. This allows each level to override settings from the previous level as appropriate.
+
+## Further reading
+
+* [AUTOTITLE](/copilot/how-tos/copilot-cli)
+* [AUTOTITLE](/copilot/reference/cli-command-reference#custom-agents-reference)
+