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 Aidas-dev/k8s-agent-skills --skill mariadb-operatorgit clone --depth 1 https://github.com/Aidas-dev/k8s-agent-skillsWrote 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/aidas-dev/k8s-agent-skills/mariadb-operator)<a href="https://agentmods.dev/skills/aidas-dev/k8s-agent-skills/mariadb-operator"><img src="https://agentmods.dev/badge/skills/aidas-dev/k8s-agent-skills/mariadb-operator/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/aidas-dev/k8s-agent-skills/mariadb-operator"><img src="https://agentmods.dev/badge/skills/aidas-dev/k8s-agent-skills/mariadb-operator.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.00046 | $0.07852 |
| Opus 5 | $0.00023 | $0.03926 |
| Sonnet 5 | $0.00009 | $0.01570 |
| Haiku 4.5 | $0.00005 | $0.00785 |
Grade A, and why
mariadb-operator 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 — 1,120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MariaDB Operator CRDs
Repository: github.com/mariadb-operator/mariadb-operator
Latest release: v26.6.0 (Jun 5, 2026)
API version: k8s.mariadb.com/v1alpha1
CRDs: 12
Kubernetes: >=1.26
Go: 1.26, controller-runtime 0.23.3
Overview
MariaDB CR ──► StatefulSet with Galera HA
MaxScale CR ──► MaxScale proxy Deployment (read/write splitting)
│
Database CR ──► Database creation
User CR ──► User creation + password rotation
Grant CR ──► Privilege assignment
│
Backup CR ──► Scheduled backups (S3/Azure/Volume)
PhysicalBackup CR ──► Physical snapshot backups
Restore CR ──► Restore from backup
PointInTimeRecovery CR ──► PITR to specific timestamp
│
Connection CR ──► Connection string in Secret
SqlJob CR ──► Scheduled SQL execution
│
ExternalMariaDB CR ──► Connect to external MariaDB instances
CRDs
| CRD | Short Name | Scope | Description |
|---|---|---|---|
MariaDB |
mdb |
Namespaced | Galera cluster |
MaxScale |
mxs |
Namespaced | MaxScale proxy |
Backup |
bmdb |
Namespaced | Logical backup |
PhysicalBackup |
pbmdb |
Namespaced | Physical snapshot |
Restore |
rmdb |
Namespaced | Restore from Backup |
PointInTimeRecovery |
pitr |
Namespaced | PITR to timestamp |
Database |
dmdb |
Namespaced | Database creation |
User |
umdb |
Namespaced | User management |
Grant |
gmdb |
Namespaced | Privilege grants |
Connection |
cmdb |
Namespaced | Connection secret |
SqlJob |
smdb |
Namespaced | SQL execution |
ExternalMariaDB |
emdb |
Namespaced | External DB connection |
MariaDB
The primary CRD defining a MariaDB Galera cluster.
apiVersion: k8s.mariadb.com/v1alpha1
kind: MariaDB
metadata:
name: mariadb-cluster
spec:
# Image (v26.3.0+: image.repo + image.tag split)
image:
repository: mariadb
tag: 11.8.8
# Galera HA
galera:
enabled: true
primary:
podIndex: 0
automaticFailover: true
config:
reuseStorageVolume: false
# Additional galera config
init:
job:
image:
repository: mariadb
tag: 11.8.8
resources: {}
# Volume claim
storage:
size: 10Gi
storageClassName: standard
# accessModes:
# - ReadWriteOnce
# - ReadWriteMany
# - ReadOnlyMany
# - ReadWriteOncePod
resizeInUseVolumes: true
waitForVolume:
enabled: false
# Replicas
replicas: 3
# Service
service:
type: ClusterIP
# Additional service template
# Connection
rootPasswordSecretKeyRef:
name: mariadb-root
key: password
# generate: true # auto-generate
username: ""
passwordSecretKeyRef: {}
database: ""
# Metrics
metrics:
enabled: true
exporter:
image:
repository: prom/mysqld-exporter
tag: v0.15.1
resources: {}
# Connection pool
connectionPool:
port: 3306
maxConnections: 100
minPoolSize: 1
# Update strategy
updateStrategy:
type: RollingUpdate
autoSwapPvc:
- statefulset-1
# Pod spec
podAnnotations: {}
imagePullSecrets: []
priorityClassName: ""
affinity: {}
tolerations: []
nodeSelector: {}
topologySpreadConstraints: []
# Resource limits
resources:
requests:
cpu: 100m
memory: 128Mi
limits:
cpu: 500m
memory: 512Mi
# TLS
tls:
enabled: false
# ssl:
# secretName: mariadb-tls
# caSecretName: mariadb-ca
# clientCertSecretName: mariadb-client
# MaxScale reference
maxScaleRef: {}
# Replication
replication:
# Source connection ref for replica
source: {}
# Maintenance
maintenance:
enabled: false
# Requeue interval during maintenance
requeueInterval: 30s
# HA
ha:
enable: true
cert: {}
# cert:
# certManager:
# enabled: true
# duration: 2160h
# Default configuration
myCnf: |
[mysqld]
character-set-server=utf8mb4
collation-server=utf8mb4_unicode_ci
max_connections=100
# PodDisruptionBudget
podDisruptionBudget:
enabled: true
maxUnavailable: 1
# Progress deadlines
progressDeadlineSeconds: 600
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 · 1,120 lines · 46 tokens per session scan A 5f329e72626d
mariadb-operator is a skill published in the GitHub repository Aidas-dev/k8s-agent-skills (2 stars, last pushed 25d ago), licensed MIT. It adds 46 tokens to every session and 7,852 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.
Other skills, from other repositories
deployment
Deploy Memoria with Docker Compose or Kubernetes. Environment variables, multi-instance setup, security. Use when deploying or configuring Memoria.
polar-local-environment
This skill should be used when setting up or managing Polar local development environment with Docker.
qdrant-deployment-options
Guides Qdrant deployment selection. Use when someone asks 'how to deploy Qdrant', 'Docker vs Cloud', 'local mode', 'embedded Qdrant', 'Qdrant EDGE', 'which deployment option', 'self-hosted vs cloud', or 'need lowest latency deployment'. Also use when choosing between deployment types for a new project.
azuresql-db-container
Runs the Azure SQL Database container (the Azure SQL Database engine) locally (Private Preview): the real PaaS engine where SERVERPROPERTY('EngineEdition') returns 5 and Edition is 'SQL Azure'. This is NOT the SQL Server image mcr.microsoft.com/mssql/server. Use when a user wants to "run Azure SQL locally", "add a…
azuresql-db-from-sql-server
Migrates a local SQL Server setup to the Azure SQL Database container for Azure-faithful local development. Use when a project already uses mcr.microsoft.com/mssql/server, mssql/server, an sqlcmd plus SA password docker setup, a "SQL Server in docker" or "local mssql container", or a docker-compose with the…
azuresql-db-schema-migration
Runs database schema migrations against the local Azure SQL Database container so the same migrations apply identically on the local engine and in the Azure cloud. Use when asked to "run my migrations against the local SQL", "apply schema to the container", "apply EF Core / dotnet ef database update", "Prisma migrate…