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/servicesgit 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.00033 | $0.01562 |
| Opus 5 | $0.00016 | $0.00781 |
| Sonnet 5 | $0.00007 | $0.00312 |
| Haiku 4.5 | $0.00003 | $0.00156 |
Grade A, and why
services 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Services (connect trust boundary)
Manage the registry that the connect server uses for authenticated HTTP and database access. All
registry operations go through the single mcp__connect__service tool; this command is a thin,
guided wrapper over its actions.
Trust invariants (enforced by the server, not this command):
-
Credentials are pinned to their registered origin (protocol + host + port) and never sent elsewhere, even in open mode.
-
The destination allowlist is on by default: registered service origins and explicitly allowlisted hosts only.
-
Read-only by default: a service opts specific HTTP methods in via
write_methods; a connection opts writes in viaallow_writes. -
Open (unrestricted) mode is human-only and out-of-band. A person edits
.goodvibes/config.json, and it is announced at session start. It reverts to restricted next session unlessdangerously_persist_across_sessionsis set. This command and theservicetool cannot flip the trust mode. -
set_authstores secrets at mode 0600 and never echoes them back; no action ever returns a secret value.getreturns an auth STATUS,list/statusreturn names and summaries only.
Usage
/goodvibes:services # list registered services + connections + allowlist
/goodvibes:services status # trust mode + persist flag + registered names + allowlist
/goodvibes:services list # registered service summaries and connection names
/goodvibes:services get <name> # credential-free summary + auth status of one service
/goodvibes:services register <name> # register an API service (guided)
/goodvibes:services remove <name> # remove a service and purge its credentials
/goodvibes:services set-auth <name> # store credentials for a service (0600, never echoed)
/goodvibes:services set-url-pattern <name> # map an extra hostname to a registered service
/goodvibes:services allow <hostname> # add a destination host to the allowlist
/goodvibes:services unallow <hostname> # remove a host from the allowlist
/goodvibes:services register-connection <name> # register a DB connection (Postgres/MySQL/SQLite)
/goodvibes:services remove-connection <name> # remove a DB connection
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.
- 3d ago First seen · 91 lines · 33 tokens per session scan A cf224cfb745b
services is a command published in the GitHub repository mgd34msu/goodvibes-plugin (6 stars, last pushed 10d ago), licensed MIT. It adds 33 tokens to every session and 1,562 once invoked, about $0.0002 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.
Other commands, from other repositories
bucket-advance
Advances a cursor to fetch or process the next batch of documents.
schema
Interactive schema design — delegates to schema-designer agent.
d1-migration
Run D1 migration workflow — generate, inspect, apply.
database-setup
Use when a project needs to store data and has no database yet. Setting up Supabase, creating tables, writing queries, and connecting them to the frontend. Written for designers.
ads_dataset-audit-generate
Inventory warehouse tables, identify duplicates, grade governance maturity.
symfony-migrations
Create and manage Doctrine migrations for database schema changes.