databases

A Seenode tool for managed MySQL and PostgreSQL databases, including their setup, settings, health, passwords, and connections to applications. MySQL and PostgreSQL are database systems used to store application data.

In plain words
What is it for?
Use it to create and inspect databases, check their state and metrics, update or rename them, rotate database passwords, and link them to Seenode applications.
Why use it?
It keeps database connection details and passwords out of chat by linking databases to apps through protected settings. It also provides checks for readiness before an app is connected.

Skill for Claude CodeCodex

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 skills/seenode/seenode-agent-plugin/databases
Any agent
npx skills add seenode/seenode-agent-plugin --skill databases
Clone the repo
git clone --depth 1 https://github.com/seenode/seenode-agent-plugin

Made for: Claude Code, Codex.

Per session 66 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 902 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.

ModelPer sessionOnce invoked
Fable 5 $0.00066 $0.00902
Opus 5 $0.00033 $0.00451
Sonnet 5 $0.00013 $0.00180
Haiku 4.5 $0.00007 $0.00090

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

Security

Grade A, and why

databases 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 yesterday.

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.

skills/databases/SKILL.md · 130 lines

How it starts

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

Seenode databases

Managed engines: MySQL and PostgreSQL. Use database_type values mysql or postgresql (never postgres).

Hard rules

  • Never fetch, echo, or ask the user to paste raw DB passwords or full connection strings into chat.
  • Wire apps with link_database_to_application (server-side copy into secret env vars).
  • After rotate_database_user_password, call link_database_to_application again with overwrite=true.
  • Poll get_database_state until ready before linking.
  • Check get_credit_balance before paid package creates/upgrades; quote pricePerMonthUsd and creditBalanceUsd (never DIY cents→dollars).
  • There is no delete/destroy database tool via MCP — send teardown to the dashboard.

Discover

list_databases(project_id=null, page=1)
get_database(database_id=...)
get_database_state(database_id=...)
list_database_packages()

Secret-looking fields (passwords, connection strings) are redacted in MCP responses. Do not hunt for connection-details patterns — use the link tool.

Create

get_credit_balance()
list_database_packages()   # optional; omit package_id for free-trial/cheapest create-enabled package
create_database(
  database_type="postgresql"|"mysql",
  database_version=null,
  custom_name=null,
  description=null,
  project_id=null,
  package_id=null
)

Provisioning is asynchronous. Poll:

get_database_state(database_id=...)

Then continue the deploy recipe (create_applicationlink_database_to_application) or link an existing app.

Metrics

get_database_metrics(database_id=..., metric_type="storage"|"connections", range_hours=1)

Use for disk pressure and connection saturation while troubleshooting.

Update metadata / package / project

update_database(
  database_id=...,
  custom_name=null,
  description=null,
  project_id=null,
  package_id=null   # paid tier; storage cannot be downgraded below data size
)

Package changes consume team credit — get explicit approval.

Read the full file on GitHub · 130 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.

  1. yesterday First seen · 130 lines · 66 tokens per session scan A aab1a010c97a

Subscribe to this mod's changes

databases is a skill published in the GitHub repository seenode/seenode-agent-plugin (2 stars, last pushed 23d ago), licensed MIT. It adds 66 tokens to every session and 902 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens