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 kouko/redshift-comment-mcp --skill redshift-grep-columnsgit clone --depth 1 https://github.com/kouko/redshift-comment-mcpWrote 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/kouko/redshift-comment-mcp/redshift-grep-columns)<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>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.00156 | $0.01034 |
| Opus 5 | $0.00078 | $0.00517 |
| Sonnet 5 | $0.00031 | $0.00207 |
| Haiku 4.5 | $0.00016 | $0.00103 |
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.
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_idorcust_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
--schemagiven: one call per listed schema. - Else:
list_schemas(include_comments=true)→ enumerate user schemas; onesearch_columnsper 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
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.
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.
- 7d ago First seen · 110 lines · 156 tokens per session scan A 6fcc07d41dae
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.
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.
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…
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…
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.
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.