$ARGUMENTS, $1, @path/to/file, !`bash`cd opencoder npm install npm run build
Then load the plugin in LM Studio:
opencoder directoryIn LM Studio chat, describe your command idea:
"Stwórz komendę do audytu bezpieczeństwa zależności w package.json"
The model will invoke refine_opencode_command and return a fully structured .md file ready for your .opencode/commands/ folder.
| Parameter | Type | Description |
|---|---|---|
refined_content | string | Complete markdown with frontmatter and <command-instruction> block |
suggested_filename | string | Kebab-case filename (e.g., security-audit.md) |
force_save | boolean | If true, saves to ./commands/ directory |
Input: "komenda do sprawdzania typów w TypeScript"
Output: check-types.md
--- description: "Run TypeScript type checking and report errors with suggested fixes" agent: build --- <command-instruction> # TypeScript Type Check ## PHASE 0: INTENT GATE Verify the project has a valid tsconfig.json... ## PHASE 1: PARALLEL ANALYSIS Launch explore agents to find... ## VERIFICATION Run `tsc --noEmit` after changes... </command-instruction>
The plugin follows the same pattern as the reference markdown-builder:
src/index.ts - Entry point registering toolssrc/toolsProvider.ts - Tool definitions with expert-level system promptstsconfig.json - TypeScript configurationname/trigger in frontmatter - filename determines command name$ARGUMENTS, @file, !`cmd`