Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add commands/mgd34msu/goodvibes-plugin/plugingit clone --depth 1 https://github.com/mgd34msu/goodvibes-pluginWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00018 | $0.01578 |
| Opus 5 | $0.00009 | $0.00789 |
| Sonnet 5 | $0.00004 | $0.00316 |
| Haiku 4.5 | $0.00002 | $0.00158 |
Grade B, and why
plugin scanned grade B with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
tail of `~/.claude/.goodvibes/deps/install.log`). How it starts
The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GoodVibes plugin
Manage the goodvibes plugin installation (intel / analytics / connect servers, hooks, and native dependencies).
Usage
/goodvibes:plugin <subcommand>
(/goodvibes:setup is the direct shortcut for /goodvibes:plugin setup, same steps.)
Subcommands
| Subcommand | Description |
|---|---|
setup |
Re-run the native dependency install in the foreground. The repair path when the automatic background install did not finish. |
status |
Show plugin health: version, server bundle, hooks, native-dependency install state. |
install-prompts |
Opt in: install a compact pointer file (may write to ~/.claude/). |
uninstall-prompts |
Cleanly remove everything install-prompts wrote. |
There is no update subcommand. Updates flow through the marketplace install path rather than a
script the plugin manages itself, so there is one update mechanism to trust instead of two that
can disagree about what version is installed.
Instructions
Parse the subcommand from $ARGUMENTS.
setup: native dependency repair
Each of the three committed server bundles externalizes a few runtime-only dependencies (native
binaries and WASM loaders that do not bundle cleanly), listed in that server's own
${CLAUDE_PLUGIN_ROOT}/server/<name>/package.json:
| Server | Runtime-only dependencies |
|---|---|
intel |
@ast-grep/napi, @vscode/ripgrep, sql.js, web-tree-sitter |
analytics |
sql.js |
connect |
sql.js (database drivers resolve from the target project, not installed here) |
Installation is automatic. The first session after a plugin install, or after an update that
changes a server's dependency list, spawns a detached background installer, which writes into
the durable home ~/.claude/.goodvibes/deps/<server>/ and links each
${CLAUDE_PLUGIN_ROOT}/server/<name>/node_modules to it. A plugin update replaces the plugin
copy but not the durable home; the SessionStart hook silently relinks at the next session.
Until an install lands, native-backed capabilities return an honest "run /goodvibes:setup"
message and everything else keeps working. Nothing crashes.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 149 lines · 18 tokens per session scan B 9ce52958c250
plugin is a command published in the GitHub repository mgd34msu/goodvibes-plugin (6 stars, last pushed 9d ago), licensed MIT. It adds 18 tokens to every session and 1,578 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.