> For the complete documentation index, see [llms.txt](https://openjs.wiki.gd/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://openjs.wiki.gd/getting-started/commands.md).

# Commands

**Main Command:** `/oj`

* This command is used to manage JavaScript scripts within the OpenJS plugin.<br>

**Subcommands**

1. **Help:**
   * Usage: `/oj help`
   * Description: Displays the usage and description of available subcommands.
2. **Version:**
   * Usage: `/oj version`
   * Description: Displays the version of this plugin.
3. **Documentation:**
   * Usage: `/oj documentation` or `/oj wiki`
   * Description: Displays the documentation link.
4. **Download link:**
   * Usage: `/oj page`
   * Description: Displays the download link for this plugin.
5. **Reload:**
   * Usage: `/oj reload` or `/oj reload <script>`
   * Description: Reloads all scripts and the config file. If a script name is specified, reloads only that script.
6. **Load:**
   * Usage: `/oj load <script>`
   * Description: Loads the specified script. The script must not be disabled.
7. **Enable:**
   * Usage: `/oj enable <script>`
   * Description: Enables and loads the specified script.
8. **Disable:**
   * Usage: `/oj disable <script>`
   * Description: Disables and unloads the specified script.
9. **List:**
   * Usage: `/oj list` or `/oj list enabled`, `/oj list disabled`, `/oj list not_loaded`
   * Description: Lists all scripts. Optionally, lists only enabled, disabled, or not loaded scripts.
10. **Converting scripts into plugins:**
    * Usage: `/oj generatePlugin <scriptPack>`
    * Description: Converts a [scriptPack](/rescources/advanced-guides.md) into a plugin, more info [here](/rescources/advanced-guides/creating-modular-scripts-and-converting-them-to-plugins.md)

## Permissions:

1. openjs.use
   * Allows using all OpenJS commands

That's actually it 😅


---

# 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://openjs.wiki.gd/getting-started/commands.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.