exclude-db-from-priming-clear

exclude-db-from-priming-clear is a skill for Claude Code from hmcts/agentic-plugins-marketplace. It costs 141 tokens per session (2,727 once invoked), scanned A, original, MIT.

A deployment-protection procedure for services with their own Postgres database. It adds that database to the exclusion list for non-production quick-clear jobs, which otherwise empty tables on a shared database server.

In plain words
What is it for?
It helps detect whether a service owns a dedicated database and raise a pull request that excludes it from the priming pipeline's quick-clear sweep.
Why use it?
It prevents test data in a dedicated service database from being removed during routine environment cleanup.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the hmcts-apim-sdlc-orchestrator plugin — 9 skills, 12 agents, 3 hooks shipped together

Good fit It helps detect whether a service owns a dedicated database and raise a pull request that excludes it from the priming pipeline's quick-clear sweep.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/hmcts/agentic-plugins-marketplace/exclude-db-from-priming-clear
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 hmcts/agentic-plugins-marketplace --skill exclude-db-from-priming-clear
Clone the repo
git clone --depth 1 https://github.com/hmcts/agentic-plugins-marketplace

Made for: Claude Code.

Or install hmcts-apim-sdlc-orchestrator, the plugin that ships this one along with the rest of its 9 skills, 12 agents, 3 hooks.

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 exclude-db-from-priming-clear

README.md
[![agentmods](https://agentmods.dev/badge/skills/hmcts/agentic-plugins-marketplace/exclude-db-from-priming-clear/github.svg)](https://agentmods.dev/skills/hmcts/agentic-plugins-marketplace/exclude-db-from-priming-clear)
Your own site
<a href="https://agentmods.dev/skills/hmcts/agentic-plugins-marketplace/exclude-db-from-priming-clear"><img src="https://agentmods.dev/badge/skills/hmcts/agentic-plugins-marketplace/exclude-db-from-priming-clear/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 exclude-db-from-priming-clear

Your own site · 80×15
<a href="https://agentmods.dev/skills/hmcts/agentic-plugins-marketplace/exclude-db-from-priming-clear"><img src="https://agentmods.dev/badge/skills/hmcts/agentic-plugins-marketplace/exclude-db-from-priming-clear.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 141 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,727 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.00141 $0.02727
Opus 5 $0.00071 $0.01363
Sonnet 5 $0.00028 $0.00545
Haiku 4.5 $0.00014 $0.00273

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

Security

Grade A, and why

exclude-db-from-priming-clear 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 10d 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/agents/hmcts-apim-sdlc-orchestrator/skills/exclude-db-from-priming-clear/SKILL.md · 266 lines

How it starts

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

Skill: Exclude Database From Priming Quick-Clear

When to invoke

  • Chained automatically from wire-service-deployment's Step 11, for any new service-cp-* that has just provisioned its own dedicated Postgres database.
  • Standalone, for an existing service-cp-* whose database was swept by a quick_clear run and needs the same protection retroactively.

Invocation command: /exclude-db-from-priming-clear

Background

hmcts/cpp-aks-ops/aks_priming_deploy.yaml runs a quick_clear job (condition: eq('${{ parameters.quick_clear }}', true)) that discovers every database on the shared nonprod Postgres flexible server — via az postgres flexible-server db list (dev) or SELECT datname FROM pg_database (non-dev) — and truncates all tables in each one, except a small hardcoded deny-list of system databases: template0, template1, postgres, repmgr, azure_maintenance, azure_sys, hrds, and any previously-excluded service databases.

Any new service database that appears on that server is swept by default. hrds already being in the deny-list shows this "add the db name to the deny-list" fix pattern is established precedent, not a new mechanism this skill invents.

This skill does not change that mechanism (see the design doc's rejected alternative — flipping to an allow-list) — it only keeps the existing deny-list current for every service-cp-*-owned database.

Step 1 — Detect a dedicated database

Run from the root of the service-cp-* repo:

python3 - <<'EOF'
import re, os

candidate = None

if os.path.exists("docker-compose.yml"):
    with open("docker-compose.yml") as f:
        m = re.search(r"POSTGRES_DB:[ \t]*(\S+)", f.read())
        if m:
            candidate = m.group(1).strip()

if not candidate and os.path.exists("src/main/resources/application.yaml"):
    with open("src/main/resources/application.yaml") as f:
        text = f.read()
    m = re.search(
        r"datasource:\s*\n\s*url:\s*.*jdbc:postgresql://[^/]+/([a-zA-Z0-9_]+)",
        text,
    )
    if m:
        candidate = m.group(1)

print(f"DB_DETECTED:{candidate}" if candidate else "NO_DB_OWNED")
EOF

Read the full file on GitHub · 266 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. 10d ago First seen · 266 lines · 141 tokens per session scan A 3c93fd54dc6b

Subscribe to this mod's changes

exclude-db-from-priming-clear is a skill published in the GitHub repository hmcts/agentic-plugins-marketplace (3 stars, last pushed yesterday), licensed MIT. It adds 141 tokens to every session and 2,727 once invoked, about $0.0007 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