A small marketplace of Claude Code plugins by StanMarek.
This repo is a Claude Code marketplace — a single git repo that ships multiple plugins. Install the marketplace once, then pick the plugins you want.
Install the marketplace:
/plugin marketplace add StanMarek/claude-plugins
Install one or more plugins from it:
/plugin install claude-faaah@stanmarek-plugins
/plugin install pastel-statusline@stanmarek-plugins
/plugin install hostile-cto@stanmarek-plugins
| Plugin | What it does |
|---|---|
claude-faaah |
Plays the iconic FAAAH sound effect on every prompt submit. |
pastel-statusline |
Three-line ANSI-colored statusline with identity, workspace, and resource info. |
hostile-cto |
An output style that turns Claude into a foul-mouthed, battle-scarred CTO who teaches through trauma. |
Hooks into UserPromptSubmit. Plays a bundled faaah.mp3 in the background using your platform's native audio player.
| Platform | Backend | Status |
|---|---|---|
| macOS | afplay |
Supported |
| Linux | paplay / aplay |
Supported |
| Windows | — | Not supported (use WSL) |
A three-line statusline:
- Line 1 (identity): vim mode · model · output style · version · agent · session · date · time
- Line 2 (workspace): cwd · git branch + status · ahead/behind · stash · last commit · project type
- Line 3 (resources): context bar · 5h limit · 7d limit · cost · lines added/removed · CPU · memory · battery
Each field gets a unique 256-color ANSI code in soft pastels.
Runtime requirements: bash, jq, git. macOS-specific commands (vm_stat, pmset) gate the memory/battery fields — those silently no-op on Linux.
An output style named "Hostile CTO". After installing, switch to it via /output-style. Claude becomes a battle-scarred, foul-mouthed CTO who responds with a Phase 1 (the rant) + Phase 2 (the lesson) structure for non-trivial work. Vulgar in language, immaculate in technical output.
Heads up: not workplace-friendly. Use accordingly.
/plugin uninstall <plugin-name>
/plugin marketplace remove stanmarek-plugins
PRs welcome. Each plugin is self-contained — keep changes focused per plugin where possible. Branch protection is enabled on main; all changes go through a pull request.
- Fork the repo
- Create a feature branch
- Submit a PR