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 skills add mgd34msu/goodvibes-plugin --skill service-integrationgit clone --depth 1 https://github.com/mgd34msu/goodvibes-pluginWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/mgd34msu/goodvibes-plugin/service-integration)<a href="https://agentmods.dev/skills/mgd34msu/goodvibes-plugin/service-integration"><img src="https://agentmods.dev/badge/skills/mgd34msu/goodvibes-plugin/service-integration/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/mgd34msu/goodvibes-plugin/service-integration"><img src="https://agentmods.dev/badge/skills/mgd34msu/goodvibes-plugin/service-integration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.1 | $0.00063 | $0.01281 |
| Opus 5 | $0.00032 | $0.00641 |
| Sonnet 5 | $0.00013 | $0.00256 |
| Haiku 4.5 | $0.00006 | $0.00128 |
Grade A, and why
service-integration 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 9d 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
service-integration
connect is the only goodvibes server that holds credentials, so it is deliberately conservative.
This skill is the usage guide for its three tools and the trust model they enforce. If you only
need to read a public web page or hit a one-off unauthenticated URL, use the native WebFetch
tool instead. connect is not a general web reader.
The three tools
| Tool | Use it for |
|---|---|
mcp__connect__service |
Registry CRUD: register/remove services and DB connections, store credentials, set read-only vs write access, manage the destination allowlist, report trust status. |
mcp__connect__api_request |
One or more HTTP requests to a registered service (or an allowlisted URL). Batched, per-entry error isolation, response capping, secret redaction on echoed responses. |
mcp__connect__db_query |
A SQL query against a registered Postgres / MySQL / SQLite connection. Read-only by default; drivers resolve from the target project. |
The /goodvibes:services command is a guided wrapper over the service tool for the common
registry operations.
Trust model (enforced by the server)
-
Credentials are pinned to their registered origin (protocol + host + port) and never sent elsewhere. Not toggleable: open mode widens where you may go, never where secrets may travel.
-
Destination allowlist is on by default. In restricted mode a destination is reachable only if its origin is a registered service origin or its host is on the allowlist. An unregistered, non-allowlisted
url(api_request) or a baredatabase_url(db_query) is refused. -
Read-only by default. HTTP write methods (anything beyond GET/HEAD/OPTIONS) require the service's
write_methodsopt-in;db_querywrites requirewrite: trueAND a target that permits writes (a connectionallow_writesopt-in, or open mode for a baredatabase_url). -
Open (unrestricted) mode is human-only and out-of-band. A person edits
.goodvibes/config.json, it is announced at session start, and it reverts to restricted the next session unless the separate, louddangerously_persist_across_sessionsflag is set. Agents cannot enable it.
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.
- 9d ago First seen · 83 lines · 63 tokens per session scan A 4f76a4b4d5fe
service-integration is a skill published in the GitHub repository mgd34msu/goodvibes-plugin (6 stars, last pushed 16d ago), licensed MIT. It adds 63 tokens to every session and 1,281 once invoked, about $0.0003 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 skills, from other repositories
event-store-design
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.
convex-explain-app
Explain an existing Convex app — data model + relationships, public vs internal functions, auth/ownership model, components, a request→data flow — read from the schema and function surface. Read-only.
platform-custom-field-generate
Use this skill when users need to create, generate, or validate Salesforce Custom Field metadata. Trigger when users mention custom fields, field types, Roll-up Summary fields, Master-Detail relationships, Lookup relationships, formula fields, picklists, dependent (controlling) picklists, referencing a value set from…
field-service-sobject-create-configure
Headless 360 REST API deployment step for creating sObject records. Handles describe-based field discovery, required-field derivation, entity-relationship ordering, and composite graph transactions. Use this skill when a designer skill (or a user directly) needs to create sObject records after design confirmation…
openloomi-api
OpenLoomi ships a local-first HTTP API served from the desktop app (port 3414, fallback 3515). All auth, Memory, AI, RAG, Loop, and Audit data live in a local SQLite database — your data stays on your machine and the OpenLoomi app is the source of truth. The only externally-routed auth path is the Composio OAuth…
nornicdb-grpc
Drive NornicDB over gRPC — the Qdrant-compatible surface (Collections, Points, Snapshots) plus the additive NornicSearch service. Use when ingesting via Qdrant SDKs, migrating from Qdrant, or running hybrid text+vector search from a non-Bolt client. Covers connection, RPC catalog, collection→database mapping…