> 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/developer-concepts/types-of-mods.md).

# Types of Mods

### Types of Starter Bricks

There are 5 different ways you can start a mod with PixieBrix:

* [**Button**](https://docs.pixiebrix.com/developing-mods/developer-concepts/types-of-mods/button.md)**:** a *customizable* button to the webpage that runs an action
* [**Context Menu**](https://docs.pixiebrix.com/developing-mods/developer-concepts/types-of-mods/context-menu-item.md)**:** a right-click menu that runs an action on the selected text or element
* [**Quick Bar Action**](https://docs.pixiebrix.com/developing-mods/developer-concepts/types-of-mods/quick-bar-action.md)**:** a menu item in the PixieBrix Quick Bar that runs an action. Learn how to set up your Quick Bar here: **Quick Bar Setup**
* [**Sidebar Panel**](https://docs.pixiebrix.com/developing-mods/developer-concepts/types-of-mods/sidebar-panel.md)**:** a custom persistent panel displayed in the PixieBrix Sidebar. You can open the sidebar by clicking the PixieBrix icon in the Chrome toolbar
* [**Trigger**](https://docs.pixiebrix.com/developing-mods/developer-concepts/types-of-mods/trigger.md)**:** an automatic trigger that runs an action. Examples of triggers are page loads, elements appearing on the screen, and more.

We call these **Starter Bricks,** and the following docs dive into each.


---

# 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/developer-concepts/types-of-mods.md?ask=<question>&goal=<user_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.
