altinity-expert-clickhouse-security

altinity-expert-clickhouse-security is a skill for Claude Code, Codex from Altinity/altinity-skills. It costs 81 tokens per session (1,841 once invoked), scanned A, original, Apache-2.0.

A read-only security-audit guide for ClickHouse databases. It reviews users, roles, permissions, settings, row policies, external data sources, audit logs, and other security controls without exposing secrets.

In plain words
What is it for?
Use it to assess ClickHouse security posture, correlate permissions with exposure and behavior, classify findings, and receive targeted remediation guidance.
Why use it?
It helps operators find security risks with evidence while avoiding destructive changes, password guessing, and disclosure of passwords or keys.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to assess ClickHouse security posture, correlate permissions with exposure and behavior, classify findings, and receive targeted remediation guidance.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/altinity/altinity-skills/altinity-expert-clickhouse-security
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 Altinity/altinity-skills --skill altinity-expert-clickhouse-security
Clone the repo
git clone --depth 1 https://github.com/Altinity/altinity-skills

Made for: Claude Code, Codex.

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 altinity-expert-clickhouse-security

README.md
[![agentmods](https://agentmods.dev/badge/skills/altinity/altinity-skills/altinity-expert-clickhouse-security/github.svg)](https://agentmods.dev/skills/altinity/altinity-skills/altinity-expert-clickhouse-security)
Your own site
<a href="https://agentmods.dev/skills/altinity/altinity-skills/altinity-expert-clickhouse-security"><img src="https://agentmods.dev/badge/skills/altinity/altinity-skills/altinity-expert-clickhouse-security/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 altinity-expert-clickhouse-security

Your own site · 80×15
<a href="https://agentmods.dev/skills/altinity/altinity-skills/altinity-expert-clickhouse-security"><img src="https://agentmods.dev/badge/skills/altinity/altinity-skills/altinity-expert-clickhouse-security.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 81 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,841 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.00081 $0.01841
Opus 5.5 $0.00032 $0.00736
Sonnet 5.5 $0.00016 $0.00368
Haiku 4.5 $0.00008 $0.00184

Measured 1mo ago against content hash 9d9be59cbb85, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

altinity-expert-clickhouse-security 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 1mo 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.

altinity-expert-clickhouse/skills/altinity-expert-clickhouse-security/SKILL.md · 90 lines

How it starts

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

ClickHouse security audit

A professional, read-only security audit from system.users, system.grants, system.roles, system.row_policies, system.settings_profile_elements, system.quotas, system.named_collections, system.functions, system.clusters and supplied configuration files. Run altinity-expert-clickhouse-connection first if the connection mode, cluster and time window are not yet established.

Core behavior

  • Work as a senior ClickHouse security reviewer. Prefer read-only SQL and metadata inspection.
  • Never run destructive SQL and never attempt online password guessing.
  • Never print secrets, password hashes, salts, private keys, access keys, tokens, or recovered password candidates.
  • Correlate findings. Do not flag a setting without considering grants, network exposure, user intent, version and observed query behavior.
  • State explicitly what could not be verified from the access you had.
  • Give remediation only when asked, and then minimally. For grant changes use the least-privilege, role-based method of the grants skill: the smallest scoped statements, roles over users, never a broad *.* grant.

Query packs

  • checks.sql — 20 checks: server identity, full SHOW ACCESS dump, user inventory with auth method and host ACL, roles and role graph, grant posture per principal, admin-equivalent and access-management holders, security-sensitive privileges, column-scoped grants, row policies, settings profiles and elements, quotas, named collection names, user-defined and executable functions, secure ports, cluster topology and the distributed user, external-engine tables and DEFINER views, logging and auth-audit baseline. Local node only; cluster-wide checks live in references/15-cluster-distributed-security.md.
  • references/ — 20 depth files, indexed below. Load only the ones a finding points at.

How to run the query packs

  1. Read each pack file from this skill's directory (the skill loader prints the directory path).
  2. Run statements one at a time, never a whole file. Statements end with ; and start with a -- @check <id> <title> header; keep the id with its result.
  3. Honor -- @requires: skip the statement when the named table is missing, when keeper is required and the server has no Keeper/ZooKeeper, or when the version condition is not met. List skipped ids with the reason.
  4. Keep {cluster} as written when a cluster macro exists; otherwise apply the connection skill's rewrite rule. Any other {placeholder} is a template variable: substitute a real value first or skip the statement.
  5. On an error, record the check id and the first line of the error, then continue. Only for UNKNOWN_IDENTIFIER, run DESCRIBE TABLE system.<table> and drop the missing column.
  6. A severity column is the verdict for that row. Copy it; do not re-grade.

Read the full file on GitHub · 90 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. 1mo ago Changed · +14 lines · -49 tokens per session 9d9be59cbb85
  2. 1mo ago First seen · 76 lines · 130 tokens per session scan A 996e2f5126df

Subscribe to this mod's changes

altinity-expert-clickhouse-security is a skill published in the GitHub repository Altinity/altinity-skills (17 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 81 tokens to every session and 1,841 once invoked, about $0.0003 per session on Opus 5.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-30.

Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

component-fixtures

Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.

microsoft/vscode · 53 tokens