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 hmcts/agentic-plugins-marketplace --skill exclude-db-from-priming-cleargit clone --depth 1 https://github.com/hmcts/agentic-plugins-marketplaceWrote 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/hmcts/agentic-plugins-marketplace/exclude-db-from-priming-clear)<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.
<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>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.00141 | $0.02727 |
| Opus 5 | $0.00071 | $0.01363 |
| Sonnet 5 | $0.00028 | $0.00545 |
| Haiku 4.5 | $0.00014 | $0.00273 |
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.
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 newservice-cp-*that has just provisioned its own dedicated Postgres database. - Standalone, for an existing
service-cp-*whose database was swept by aquick_clearrun 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
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.
- 10d ago First seen · 266 lines · 141 tokens per session scan A 3c93fd54dc6b
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.
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.
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.
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 …
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…
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.
polar-local-environment
This skill should be used when setting up or managing Polar local development environment with Docker.