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-helmgit 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-helm)<a href="https://agentmods.dev/skills/aidas-dev/k8s-agent-skills/mariadb-helm"><img src="https://agentmods.dev/badge/skills/aidas-dev/k8s-agent-skills/mariadb-helm/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-helm"><img src="https://agentmods.dev/badge/skills/aidas-dev/k8s-agent-skills/mariadb-helm.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.00035 | $0.03649 |
| Opus 5 | $0.00017 | $0.01825 |
| Sonnet 5 | $0.00007 | $0.00730 |
| Haiku 4.5 | $0.00003 | $0.00365 |
Grade A, and why
mariadb-helm 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 — 384 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MariaDB Operator — Helm Charts
Repository: https://mariadb-operator.github.io/mariadb-operator
OCI: oci://ghcr.io/mariadb-operator/charts
Charts (3)
| Chart | Latest | Purpose |
|---|---|---|
mariadb-operator-crds |
26.6.0 | CRDs only (recommended: manage separately) |
mariadb-operator |
26.6.0 | Controller + cert-controller + webhook + metrics |
mariadb-cluster |
26.6.0 | MariaDB cluster + MaxScale + backups + users |
App version: 26.6.0
Images: ghcr.io/mariadb-operator/mariadb-operator:26.6.0 (single image used for controller, webhook, cert-controller)
Quick Install
helm repo add mariadb-operator https://mariadb-operator.github.io/mariadb-operator
helm repo update
# 1. Install CRDs (separate chart to prevent accidental deletion)
helm install mariadb-operator-crds mariadb-operator/mariadb-operator-crds \
--version 26.6.0
# 2. Install operator
helm install mariadb-operator mariadb-operator/mariadb-operator \
--namespace mariadb-operator --create-namespace \
--version 26.6.0
# 3. (Optional) Provision a MariaDB cluster
helm install mariadb-cluster mariadb-operator/mariadb-cluster \
--namespace mariadb-operator \
--version 26.6.0
Using OCI Registry
helm pull oci://ghcr.io/mariadb-operator/charts/mariadb-operator --version 26.6.0
helm pull oci://ghcr.io/mariadb-operator/charts/mariadb-operator-crds --version 26.6.0
helm pull oci://ghcr.io/mariadb-operator/charts/mariadb-cluster --version 26.6.0
mariadb-operator-crds
Manages CRDs independently. Safer than crds.enabled: true on the operator chart.
helm install mariadb-operator-crds mariadb-operator/mariadb-operator-crds \
--version 26.6.0
This chart has no values — it only ships CRDs.
mariadb-operator
Deploys the controller, webhook, cert-controller, RBAC, service accounts, and ServiceMonitors.
Requirements
- Kubernetes >= 1.26
- Prometheus operator (optional, for ServiceMonitors)
- cert-manager (optional, for webhook certs — otherwise cert-controller handles them)
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 · 384 lines · 35 tokens per session scan A ee35329231fd
mariadb-helm is a skill published in the GitHub repository Aidas-dev/k8s-agent-skills (2 stars, last pushed 26d ago), licensed MIT. It adds 35 tokens to every session and 3,649 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…