> For the complete documentation index, see [llms.txt](https://gitbook.opensocial.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gitbook.opensocial.co/features/plugins.md).

# Plugins

Tribe owners can further customise their Tribe by including additional functions through the use of Plugins, such as issuing tokens, bounty, predictions, trivia, investment, membership and DAO tools. Tribe owners purchase Plugin NFTs providing the licence to use such Plugins. In addition, Plugin NFTs bought by the Tribe owner are attached to the Tribe NFT. If the Tribe NFT ownership is transferred, the corresponding licence to use such Plugins will also be transferred.

Plugin NFTs are supported by ERC-1155

### Open Link

\
Developers are welcome to build different Plugins and can derive earnings based on usage by Tribe owners. Plugins used on third party Web3 dApps can be connected and made available to the OpenSocial protocol through OpenLink, which will share the Plugin to the OpenSocial protocol via an on-chain post.&#x20;

<br>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://gitbook.opensocial.co/features/plugins.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.