redshift-grep-columns

redshift-grep-columns is a skill for Claude Code from kouko/redshift-comment-mcp. It costs 156 tokens per session (1,034 once invoked), scanned A, original, MIT.

A search for Amazon Redshift columns across many tables and schemas. It matches words in column names and descriptions, where a schema is a named group that organizes database tables.

In plain words
What is it for?
Use it before joining tables to find matching fields, or to check whether teams use consistent column names.
Why use it?
It helps find shared keys or related fields when you know the concept but not the table containing it.

Skill for Claude Code

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

Part of the redshift-comment-mcp plugin — 7 skills, 7 commands, 1 MCP server shipped together

Good fit Use it before joining tables to find matching fields, or to check whether teams use consistent column names.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/kouko/redshift-comment-mcp/redshift-grep-columns
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 kouko/redshift-comment-mcp --skill redshift-grep-columns
Clone the repo
git clone --depth 1 https://github.com/kouko/redshift-comment-mcp

Made for: Claude Code.

Or install redshift-comment-mcp, the plugin that ships this one along with the rest of its 7 skills, 7 commands, 1 MCP server.

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 redshift-grep-columns

README.md
[![agentmods](https://agentmods.dev/badge/skills/kouko/redshift-comment-mcp/redshift-grep-columns.svg)](https://agentmods.dev/skills/kouko/redshift-comment-mcp/redshift-grep-columns)
Your own site
<a href="https://agentmods.dev/skills/kouko/redshift-comment-mcp/redshift-grep-columns"><img src="https://agentmods.dev/badge/skills/kouko/redshift-comment-mcp/redshift-grep-columns.svg" alt="Measured on agentmods" height="20"></a>
Per session 156 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,034 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.00156 $0.01034
Opus 5 $0.00078 $0.00517
Sonnet 5 $0.00031 $0.00207
Haiku 4.5 $0.00016 $0.00103

Measured 7d ago against content hash 6fcc07d41dae, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

redshift-grep-columns 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 7d 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.

skills/redshift-grep-columns/SKILL.md · 110 lines

How it starts

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

Redshift Cross-Table Column Grep

Find every column whose name or comment matches a keyword across all tables in one or all schemas. Single MCP call per schema via search_columns(table_name=None).

When to use / NOT

  • Use to find FK / shared-key columns across many tables (typical pre-JOIN reconnaissance).
  • Use to audit naming consistency ("are we calling this customer_id or cust_no?").
  • NOT for a single known table — use MCP search_columns(kw, schema, table) directly.
  • NOT for single-column lookup — use MCP get_column_comment.
  • NOT for table-name search — use /redshift-grep-tables.

Inputs

Form Behavior
<keyword> grep across all schemas in the cluster
<keyword> --schema <name> scope to one schema
<keyword> --schema <s1>,<s2> scope to listed schemas
<kw1> <kw2> space-separated keywords (OR logic on MCP side)
--max-list N results per page (default 50)

Flow

Step 1 — schema-wide search via MCP

The MCP server's search_columns accepts an optional table_name; omit it for schema-wide column search in one call:

search_columns(keywords, schema_name=<schema>, table_name=None)

This returns one row per matching column with table_name included, ranked by hit_count across name + comment. Paginate via has_more if total > 50.

Procedure:

  • If --schema given: one call per listed schema.
  • Else: list_schemas(include_comments=true) → enumerate user schemas; one search_columns per schema (schema-wide each).
  • Aggregate.

Latency: ~0.7s per schema-wide call (12K-column schemas). For clusters with many schemas, prompt user to scope via --schema before running.

Step 2 — render

Group by <schema>.<table>, comment-first. One blank line between groups:

Matches for "customer_id" (12 hits in 3 schemas, 8 tables):

dbt_marts.fct_orders
  customer_id   bigint   Customer reference (FK to dim_users.id)

dbt_marts.fct_returns
  customer_id   bigint   Customer who initiated the return

dbt_staging.stg_users
  id            bigint   Customer's primary key
  cust_no       bigint   Legacy customer no, alias for id

Read the full file on GitHub · 110 lines

Files

What ships with it

3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 7d ago First seen · 110 lines · 156 tokens per session scan A 6fcc07d41dae

Subscribe to this mod's changes

redshift-grep-columns is a skill published in the GitHub repository kouko/redshift-comment-mcp (1 stars, last pushed 2mo ago), licensed MIT. It adds 156 tokens to every session and 1,034 once invoked, about $0.0008 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

schema-exploration

Lists tables, describes columns and data types, identifies foreign key relationships, and maps entity relationships in a database. Use when the user asks about database schema, table structure, column types, what tables exist, ERD, foreign keys, or how entities relate.

langchain-ai/deepagents · 57 tokens

ha-data-stores

Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…

shiwenwen/hope-agent · 115 tokens

supabase

Supabase / PostgREST Row-Level-Security playbook — pull the anon (or leaked servicerole) key out of the frontend JS, map tables from the auto-generated OpenAPI spec, test anonymous RLS READ disclosures (PII/secret leaks), and anonymous RLS WRITE abuse (insert/update/delete — e.g. forging…

PentesterFlow/agent · 120 tokens

nornicdb-cypher-queries

Pick fast, predictable Cypher query shapes in NornicDB — point lookups, batch retrieval, pagination, search, traversal, batched UNWIND/MERGE writes, cleanup, multi-tenant isolation. Use when writing or reviewing Cypher whose latency or throughput matters; maps user intent to the executor's hot-path query templates.

orneryd/NornicDB · 79 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