A manual repair command that re-runs GoodVibes' installation of native dependencies in the foreground, so you can see its output.

Use it after installing or updating the plugin when native dependencies are missing or an automatic install failed.

It helps when the automatic background installation did not finish. Native-backed tools may not work until these dependencies are installed.

setup — Command by mgd34msu

Install

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.

agentmods

npx agentmods add commands/mgd34msu/goodvibes-plugin/setup

Clone the repo

git clone --depth 1 https://github.com/mgd34msu/goodvibes-plugin

Per session 25 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 644 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What 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.00025	$0.00644
Opus 5	$0.00013	$0.00322
Sonnet 5	$0.00005	$0.00129
Haiku 4.5	$0.00003	$0.00064

Measured 2d ago against content hash bae51eee51a2, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

setup scanned grade A with 0 findings 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.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/goodvibes/commands/setup.md · 59 lines

How it starts

The opening of the file, as written. The whole thing — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.

GoodVibes setup (manual repair)

Native dependencies normally install automatically. The first session after a plugin install, or after an update that changes a server's dependency list, spawns a detached background installer, and the tools are ready by the next session. This command is the repair path for when that did not work. It re-runs the same installer in the foreground so the output is visible.

Per-server runtime-only dependencies (native binaries and WASM loaders that do not bundle cleanly, listed in ${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)

Installs land in the durable home ~/.claude/.goodvibes/deps/<server>/, and each ${CLAUDE_PLUGIN_ROOT}/server/<name>/node_modules is a link to it, so installs survive plugin updates (the SessionStart hook relinks after an update). Until an install lands, the servers still boot and every non-native capability works; native-backed capabilities return an honest pointer here instead of crashing.

Instructions

Check the install state per server (a representative dependency probes each):

for s in intel analytics connect; do
  case $s in
    intel) probe="@ast-grep/napi" ;;
    analytics) probe="sql.js" ;;
    connect) probe="sql.js" ;;
  esac
  test -d "${CLAUDE_PLUGIN_ROOT}/server/$s/node_modules/$probe" && echo "$s: INSTALLED" || echo "$s: NEEDS_INSTALL"
done

If every server reports INSTALLED, report that and stop.

Run the installer in the foreground. It is safe to run repeatedly, because servers that are already installed are skipped and a stale lock older than 10 minutes is ignored.
```
node "${CLAUDE_PLUGIN_ROOT}/hooks/lib/deps-install.mjs" "${CLAUDE_PLUGIN_ROOT}"
```
Read ~/.claude/.goodvibes/deps/.last-result.json and report the outcome. On success:
```
Native dependencies installed for intel, analytics, and connect. goodvibes' structure-aware
search/analysis, the analytics report, and registered service access are ready.
```
On failure, name the failing servers and show the relevant tail of ~/.claude/.goodvibes/deps/install.log.

Read the full file on GitHub · 59 lines

Changes

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 · 59 lines · 25 tokens per session scan A bae51eee51a2

Subscribe to this mod's changes

setup is a command published in the GitHub repository mgd34msu/goodvibes-plugin (6 stars, last pushed 9d ago), licensed MIT. It adds 25 tokens to every session and 644 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

setup

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

GoodVibes setup (manual repair)

Instructions

What this file has done since we first saw it

Other commands, from other repositories

git

checklist

clarify

specify

analyze

constitution