> For the complete documentation index, see [llms.txt](https://docs.pixiebrix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pixiebrix.com/developing-mods/sharing-mods/saving-a-mod.md).
# Saving a Mod
You'll need to save a mod before closing the Page Editor if you want to use the mod on other pages, or share with a team.
### Click the Save button at the top right of the Page Editor toolbar
{% hint style="info" %}
If it's your first time saving a mod, you'll be prompted to create a username.
{% endhint %}
### Review Save Fields
When packaging a mod, PixieBrix prompts you for the following information
* ID: a unique identification for the mod. It must start with your author scope or an author scope of a team where you have a Developer role.
* ***Note that if you want to deploy a mod to your team or you want your team to have the ability to edit a mod, you’ll want to select the team alias (the @ field at the start of the mod ID, before the /).***
* Name: a human-readable name for the mod
* Version: a version number, in the format `major.minor.patch`. For example 1.0.0
* Description: a helpful description that describes what the mod is for
{% hint style="info" %}
**Pro-Tip:** Add a “collection” part to the mod id to help organize your mods. For example `@username/slack/send-slack-message` instead of `@username/send-slack-message`
{% endhint %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.pixiebrix.com/developing-mods/sharing-mods/saving-a-mod.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
