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 StarRocks/starrocks-debug-skills --skill high-concurrencygit clone --depth 1 https://github.com/StarRocks/starrocks-debug-skillsWrote 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/starrocks/starrocks-debug-skills/high-concurrency)<a href="https://agentmods.dev/skills/starrocks/starrocks-debug-skills/high-concurrency"><img src="https://agentmods.dev/badge/skills/starrocks/starrocks-debug-skills/high-concurrency/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/starrocks/starrocks-debug-skills/high-concurrency"><img src="https://agentmods.dev/badge/skills/starrocks/starrocks-debug-skills/high-concurrency.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.00083 | $0.05790 |
| Opus 5 | $0.00042 | $0.02895 |
| Sonnet 5 | $0.00017 | $0.01158 |
| Haiku 4.5 | $0.00008 | $0.00579 |
Grade C, and why
high-concurrency scanned grade C with 2 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 10d 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
curl -s "http://$be:8040/api/query_cache/stat" | python3 -m json.tool 2>/dev/null | grep -E "hit|miss|ratio" Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s "http://<be_host>:<be_http_port>/metrics" | grep query_cache_hit_ratio How it starts
The opening of the file, as written. The whole thing — 579 lines — stays where its author put it; the contents beside it link to each section on GitHub.
High-Concurrency Best Practices
Investigation and tuning guide for high-QPS workloads: data modeling, primary-key optimization, query cache, pipeline parallelism, connection pooling, and emergency load disabling.
Five root causes account for most high-concurrency performance problems:
- Cause A — Connection pool exhausted (too many connections, no client pool)
- Cause B — FE planning CPU saturation (complex queries, no plan cache)
- Cause C —
pipeline_doptoo high for short queries (scheduling overhead) - Cause D — Session-level timeout override causing memory volatility
- Cause E — Query cache not effective (low hit ratio, wrong workload type)
Metric Taxonomy — Read This First
Before tuning, establish a baseline measurement of the current state.
FE connection metrics
| Metric / Observable | Meaning |
|---|---|
Connection count approaching qe_max_connection |
Connection layer bottleneck |
SHOW PROC '/current_queries' count |
Active concurrent queries right now |
FE log Reach limit of connections |
Connection limit hit — new clients rejected |
How to retrieve:
# Check qe_max_connection setting
grep "qe_max_connection" fe/conf/fe.conf
# Default: 1024
# Count active connections via SQL
# (run on FE that is not itself overloaded)
SELECT COUNT(*) FROM information_schema.processlist;
# Or check current queries
# SHOW PROC '/current_queries';
Query cache metrics
| Metric | Meaning |
|---|---|
starrocks_be_query_cache_hit_ratio |
Cache hit ratio (0–1); <0.1 = cache not effective |
query_cache_capacity (BE config) |
Total cache size allocated per BE |
How to retrieve:
# Per-BE cache hit ratio (Prometheus metric)
curl -s "http://<be_host>:<be_http_port>/metrics" | grep query_cache_hit_ratio
# Detailed cache stats per BE
curl -s "http://<be_host>:<be_http_port>/api/query_cache/stat"
Pipeline parallelism metrics
| Metric / Observable | Meaning |
|---|---|
pipeline_dop current session value |
Degree of parallelism per query fragment |
SHOW PROC '/current_queries' → many queries in RUNNING |
Queries competing for pipeline threads |
What ships with it
1 file 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.
- 10d ago First seen · 579 lines · 83 tokens per session scan C c8f4ceab7f8b
high-concurrency is a skill published in the GitHub repository StarRocks/starrocks-debug-skills (75 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 83 tokens to every session and 5,790 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for prisma-next. Use when the user wants to create a pull request, open a PR, or submit changes for review.
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…