# Oosh Module > Create a new module for an oosh CLI. Use /oosh-module to generate an annotated .sh file in the CLI's modules directory. Trigger when the user wants to add a command, module, or feature to an existing oosh CLI. Use when this capability is needed. - Skill: `tomevault-io/oosh-module` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/oosh-module` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/oosh-module/raw - Safety review: pending (external: skill-scanner PASS, skillspector PASS) - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: tomevault-io (https://skillmd.com/u/tomevault-io) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/tomevault-io/oosh-module --- # /oosh-module — Create a new module Create a new module file in the CLI's modules directory. ## Steps 1. Determine the modules path: `~/./modules/` (default) — if the CLI was generated to a custom path, ask the user 2. Ask what commands and flags the module should expose 3. Write `.sh` following the conventions below 4. Run `oosh lint ` to validate the new module ## Conventions Read `references/annotations.md` in this skill directory for the full annotation reference and module template. Key rules: - File starts with `#!/bin/bash` and `#@module - ` - Import the engine: `. ${MODULES_DIR}/../oo.sh` - Variable names: `UPPER_SNAKE_CASE`, prefixed with module name (e.g., `DEPLOY_ENV` in `deploy.sh`) - End with `main $0 "$@"` - No `sed`, `awk`, `grep` in hot paths — bash builtins only - Bash 3.2 compatible --- > Source: [bruno-de-queiroz/oosh](https://github.com/bruno-de-queiroz/oosh) — distributed by [TomeVault](https://tomevault.io).