db-upgrader

db-upgrader is a skill for Claude Code from RedHatInsights/platform-frontend-ai-toolkit. It costs 34 tokens per session (1,930 once invoked), scanned A, original, Apache-2.0.

A utility for editing YAML configuration files during RDS PostgreSQL upgrades. YAML is a text format commonly used for application and deployment settings.

In plain words
What is it for?
Running upgrade steps such as checking replication slots, preparing maintenance work, updating switchover settings, and creating SQL query files.
Why use it?
It reduces manual changes to upgrade flags, database versions, maintenance steps, and SQL files.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the infrastructure-plugin plugin — 1 skill, 8 agents shipped together

Good fit Running upgrade steps such as checking replication slots, preparing maintenance work, updating switchover settings, and creating SQL query files.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/redhatinsights/platform-frontend-ai-toolkit/db-upgrader
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.

Any agent
npx skills add RedHatInsights/platform-frontend-ai-toolkit --skill db-upgrader
Clone the repo
git clone --depth 1 https://github.com/RedHatInsights/platform-frontend-ai-toolkit

Made for: Claude Code.

Or install infrastructure-plugin, the plugin that ships this one along with the rest of its 1 skill, 8 agents.

Wrote 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.

agentmods badge for db-upgrader

README.md
[![agentmods](https://agentmods.dev/badge/skills/redhatinsights/platform-frontend-ai-toolkit/db-upgrader/github.svg)](https://agentmods.dev/skills/redhatinsights/platform-frontend-ai-toolkit/db-upgrader)
Your own site
<a href="https://agentmods.dev/skills/redhatinsights/platform-frontend-ai-toolkit/db-upgrader"><img src="https://agentmods.dev/badge/skills/redhatinsights/platform-frontend-ai-toolkit/db-upgrader/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.

agentmods 80×15 button for db-upgrader

Your own site · 80×15
<a href="https://agentmods.dev/skills/redhatinsights/platform-frontend-ai-toolkit/db-upgrader"><img src="https://agentmods.dev/badge/skills/redhatinsights/platform-frontend-ai-toolkit/db-upgrader.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,930 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00034 $0.01930
Opus 5 $0.00017 $0.00965
Sonnet 5 $0.00007 $0.00386
Haiku 4.5 $0.00003 $0.00193

Measured 9d ago against content hash 3fa4146acb21, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

db-upgrader 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.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/helper.js), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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/infrastructure/skills/db-upgrader/SKILL.md · 268 lines

How it starts

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

Database Upgrader YAML Utilities

This skill provides utilities for modifying YAML files during RDS database upgrades. It can be called by db upgrade agents or invoked directly by users.

Invoking the Skill

You can call this skill with arguments:

/db-upgrader <service> <environment> <version> [product] [action]

Examples:

# Run orchestrator to determine next step
/db-upgrader chrome-service stage 16.9

# Run specific upgrade step
/db-upgrader chrome-service production 16.9 insights status-page
/db-upgrader chrome-service stage 16.9 insights replication-check
/db-upgrader chrome-service stage 16.9 insights switchover

The skill will automatically collect:

  • $ARGUMENTS.service - Service name (required)
  • $ARGUMENTS.environment - Environment: stage or production (required)
  • $ARGUMENTS.version - Target PostgreSQL version (required)
  • $ARGUMENTS.product - Product/bundle name (optional, defaults to "insights")
  • $ARGUMENTS.action - Upgrade step to perform (optional)
    • status-page - Create status page maintenance (production only)
    • replication-check - Verify no active replication slots
    • post-maintenance - Create VACUUM and REINDEX queries
    • switchover - Trigger database version switch
    • cleanup - Remove blue/green deployment config

Available Operations

1. Update Switchover Flags

Update switchover and delete flags in a namespace YAML file.

Input: Path to namespace YAML file Action: Changes switchover: false to switchover: true and delete: false to delete: true

Example:

# Before
blue_green_deployment:
  enabled: true
  switchover: false
  delete: false
  target:
    engine_version: "16.9"

# After
blue_green_deployment:
  enabled: true
  switchover: true
  delete: true
  target:
    engine_version: "16.9"

2. Update Engine Version

Update the engine_version field in an RDS YAML file.

Input:

  • Path to RDS YAML file
  • New version string (e.g., "16.9")

Action: Replaces the engine_version value with the new version

Read the full file on GitHub · 268 lines

Files

What ships with it

3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 9d ago First seen · 268 lines · 34 tokens per session scan A 3fa4146acb21

Subscribe to this mod's changes

db-upgrader is a skill published in the GitHub repository RedHatInsights/platform-frontend-ai-toolkit (5 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 34 tokens to every session and 1,930 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.

Related

Other skills, from other repositories

alloydb-basics

Manages clusters, instances, and backups for AlloyDB for PostgreSQL, and integrates with AlloyDB Model Context Protocol (MCP) tools for automated database operations. Use when creating, configuring, or administering AlloyDB databases. Do NOT use for general PostgreSQL instances (e.g. Cloud SQL) or other GCP databases.

google/skills · 72 tokens

postgresql-table-design

Use this skill when designing or reviewing a PostgreSQL-specific schema. Covers best-practices, data types, indexing, constraints, performance patterns, and advanced features.

wshobson/agents · 37 tokens

db-repair

Auto-fix gbrain's Postgres access so the brain stays available. When any gbrain command or MCP tool result carries a GBRAINDBACCESS marker (or an operator reports the brain database is down), run the hardcoded gbrain db-repair ladder: diagnose, apply the safe tier, verify. The action is ALWAYS the hardcoded command …

garrytan/gbrain · 96 tokens

dsql

Build with Aurora DSQL — manage schemas, execute queries, handle migrations, diagnose query plans, diagnose cluster performance, load data, and develop applications with a serverless, distributed SQL database. Covers IAM auth, multi-tenant patterns, MySQL-to-DSQL and PostgreSQL-to-DSQL schema conversion, foreign key…

awslabs/agent-plugins · 229 tokens

volcengine-rds-postgresql

A tool for operating PostgreSQL databases hosted by Volcano Engine's managed database service. PostgreSQL is a relational database used to store structured application data.

bytedance/agentkit-samples · 63 tokens

polar-local-environment

This skill should be used when setting up or managing Polar local development environment with Docker.

fcakyon/claude-codex-settings · 22 tokens