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 agentmods add commands/kouko/redshift-comment-mcp/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/commands/kouko/redshift-comment-mcp/redshift-grep-columns)<a href="https://agentmods.dev/commands/kouko/redshift-comment-mcp/redshift-grep-columns"><img src="https://agentmods.dev/badge/commands/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 | $0.00041 | $0.00179 |
| Opus 5 | $0.00020 | $0.00089 |
| Sonnet 5 | $0.00008 | $0.00036 |
| Haiku 4.5 | $0.00004 | $0.00018 |
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 5d 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.
What it actually says
Use the redshift-comment-mcp:redshift-grep-columns skill to find columns by keyword across many tables. Argument forms accepted:
/redshift-grep-columns <keyword>(all schemas)/redshift-grep-columns <keyword> --schema <s>(scope to one schema)/redshift-grep-columns <keyword> --schema <s1>,<s2>(scope to listed schemas)/redshift-grep-columns <kw1> <kw2>(AND across keywords)/redshift-grep-columns <keyword> --max-list 30(results per page)
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.
- 5d ago First seen · 12 lines · 41 tokens per session scan A 3a77334d29a3
redshift-grep-columns is a command published in the GitHub repository kouko/redshift-comment-mcp (1 stars, last pushed 2mo ago), licensed MIT. It adds 41 tokens to every session and 179 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 commands, from other repositories
review-renovate
Review and merge renovate PRs with automerge configuration updates.
monitor-ci
Monitors pull request CI checks until they are resolved (pass or fail).
plan-regression-tests
Plan regression tests for existing code with it.skip statements.
init
Initialize configurations for Supabase local development.
volume-admin-set-status
Changes the operational status of a named volume.
database-setup
Use when a project needs to store data and has no database yet. Setting up Supabase, creating tables, writing queries, and connecting them to the frontend. Written for designers.