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 aiocean/claude-plugins --skill aio-starrocks-query-tuninggit clone --depth 1 https://github.com/aiocean/claude-pluginsWrote 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/aiocean/claude-plugins/aio-starrocks-query-tuning)<a href="https://agentmods.dev/skills/aiocean/claude-plugins/aio-starrocks-query-tuning"><img src="https://agentmods.dev/badge/skills/aiocean/claude-plugins/aio-starrocks-query-tuning/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/aiocean/claude-plugins/aio-starrocks-query-tuning"><img src="https://agentmods.dev/badge/skills/aiocean/claude-plugins/aio-starrocks-query-tuning.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.00102 | $0.04864 |
| Opus 5 | $0.00051 | $0.02432 |
| Sonnet 5 | $0.00020 | $0.00973 |
| Haiku 4.5 | $0.00010 | $0.00486 |
Grade A, and why
aio-starrocks-query-tuning 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.
How it starts
The opening of the file, as written. The whole thing — 606 lines — stays where its author put it; the contents beside it link to each section on GitHub.
StarRocks Query Tuning
Complete reference from docs.starrocks.io/docs/best_practices/query_tuning/.
Related Skills
/aio-starrocks-best-practices— Table design: partitioning, bucketing, sort keys, PK tuning/starrocks— Query syntax, cluster connections, Grafana integration (external skill, not part of this plugin)/starrocks-expert— General table types, data loading, materialized views (external skill, not part of this plugin)
1. Tuning Methodology — Top-Down Diagnostic
Five-step process, always in order:
- Identify — Use monitoring, query history, audit logs to detect slow queries or resource bottlenecks
- Collect & Analyze —
EXPLAIN/EXPLAIN ANALYZE+ Query Profile for detailed metrics - Locate Root Cause — Pinpoint problematic operators: join order, missing indexes, data distribution, SQL inefficiencies
- Apply Tuning — SQL rewriting, schema optimization, query hints, session variables
- Validate & Iterate — Rerun, compare metrics, review plans, continue optimizing
2. Query Plans — EXPLAIN Variants
Commands
| Command | What It Shows | When to Use |
|---|---|---|
EXPLAIN LOGICAL |
Simplified logical plan | Quick overview |
EXPLAIN |
Basic physical plan | Standard analysis |
EXPLAIN VERBOSE |
Detailed physical plan with extensive info | Deep investigation |
EXPLAIN COSTS |
Physical plan + cost estimates per operation | Cost comparison |
EXPLAIN ANALYZE |
Executes query + actual runtime statistics | Production diagnosis |
-- Quick check
EXPLAIN SELECT shop_id, SUM(net_sales) FROM sales WHERE shop_id = 123 GROUP BY shop_id;
-- Deep investigation
EXPLAIN VERBOSE SELECT ...;
-- Actual execution stats (runs the query!)
EXPLAIN ANALYZE SELECT ...;
Plan Hierarchy
Plans are structured in 3 levels — read bottom-up starting from scan nodes:
- Fragment — Top-level work units distributed to BEs. Spawn FragmentInstances.
- Pipeline — Chain of operators within a fragment. Concurrent PipelineDrivers.
- Operator — Atomic execution steps: scan, join, aggregate, sort, exchange, etc.
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 · 606 lines · 102 tokens per session scan A bab435054df1
aio-starrocks-query-tuning is a skill published in the GitHub repository aiocean/claude-plugins (4 stars, last pushed 6d ago), licensed MIT. It adds 102 tokens to every session and 4,864 once invoked, about $0.0005 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-09-03.
Other skills, from other repositories
optimize
Analyze and suggest performance improvements for code, queries, or systems.
memstack-security-rls-checker
Use this skill when the user says 'check RLS', 'audit RLS', 'RLS policies', 'row level security', 'Supabase security audit', or needs to verify table-level access control. Audits Supabase Row Level Security policies across all tables. Do NOT use for non-Supabase projects or writing RLS policies from scratch.
memstack-security-rls-guardian
Use this skill when creating or altering database tables in Supabase or PostgreSQL projects. Triggers include: CREATE TABLE, ALTER TABLE, migration files, 'RLS', 'row level security', 'new table', 'database schema'. Enforces Row Level Security policies on every table to prevent unauthorized data access. Do NOT use for…
source-command-audit-whitepapers
Audit version freshness, FR/EN parity, and metadata quality of all whitepapers and recap cards.
audit-agents-skills
Audit Claude Code agents, skills, and commands for quality and production readiness. Use when evaluating skill quality, checking production readiness scores, or comparing agents against best-practice templates.
design-patterns
Detect, suggest, and evaluate GoF design patterns in TypeScript/JavaScript codebases. Use when refactoring code, applying singleton/factory/observer/strategy patterns, reviewing pattern quality, or finding stack-native alternatives for React, Angular, NestJS, and Vue.