Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
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.
[](https://agentmods.dev/skills/starrocks/starrocks-debug-skills/tablet)<a href="https://agentmods.dev/skills/starrocks/starrocks-debug-skills/tablet"><img src="https://agentmods.dev/badge/skills/starrocks/starrocks-debug-skills/tablet.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.00085 | $0.05752 |
| Opus 5 | $0.00043 | $0.02876 |
| Sonnet 5 | $0.00017 | $0.01150 |
| Haiku 4.5 | $0.00009 | $0.00575 |
Grade A, and why
tablet scanned grade A with 1 finding 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 6d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
**Option 2 — curl BE HTTP port (compaction and rowset state)** How it starts
The opening of the file, as written. The whole thing — 658 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tablet Governance
Investigation guide for tablet health, balance, data skew, bucket optimization, and version-count / compaction-lag issues.
Five root causes account for the vast majority of cases:
- Cause A — data skew from low-cardinality bucket key
- Cause B — too many versions (compaction lag)
- Cause C — error state replicas (VERSION_ERROR, SCHEMA_ERROR)
- Cause D — too many tablets (over-sharding from fine partitions or excess buckets)
- Cause E — disk balance retry loop (metadata state inconsistency)
Metric Taxonomy — Read This First
Before using any metrics, understand the two-layer observability structure:
SQL-based observability
SHOW TABLET FROM <table> — per-tablet summary for a table:
| Field | Meaning |
|---|---|
TabletId |
Tablet identifier |
ReplicaId |
Replica identifier on a specific BE |
BackendId |
BE hosting this replica |
SchemaHash |
Schema version hash (mismatch indicates SCHEMA_ERROR) |
Version |
Latest visible version |
VersionCount |
Number of versions (rowsets) tracked by the system |
LstFailedVersion |
Last version that failed to load — non-zero indicates replica problem |
LstSuccessVersion |
Last version successfully applied |
DataSize |
Storage size of this replica in bytes |
RowCount |
Row count estimate |
State |
Replica state: NORMAL, CLONE, SCHEMA_CHANGE, ALTER |
SHOW TABLET <tablet_id> — single tablet detail:
| Field | Meaning |
|---|---|
DbName / TableName / PartitionName |
Context for this tablet |
State |
Tablet state |
VersionCount |
Version count across replicas (from detailcmd) |
CompactionStatus URL |
Link to BE compaction state JSON — shows last_base_compaction_time, cumulative_layer_point |
information_schema.be_tablets — per-replica metrics from BE (most detailed):
| Field | Meaning |
|---|---|
be_id |
BE hosting this replica |
tablet_id |
Tablet identifier |
num_version |
Total version count (all edits ever) |
num_rowset |
Active rowsets in current version — key compaction health indicator |
num_segment |
Segment files (num_rowset × segments per rowset) |
data_size |
Raw data size in bytes |
num_row |
Row count |
state |
Replica state |
medium_type |
HDD or SSD |
What ships with it
4 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.
- 6d ago First seen · 658 lines · 85 tokens per session scan A 99e8d2f582b4
tablet is a skill published in the GitHub repository StarRocks/starrocks-debug-skills (75 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 85 tokens to every session and 5,752 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (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
safe-sql-execution
Use whenever code will build, return, fetch, or execute SQL that runs against a user's real Postgres database — even when the request reads like an ordinary feature or bug fix and never says "security," "injection," or "SafeSqlFragment." This covers: writing or editing any pg-meta function, query builder, or endpoint…
write-the-docs
Draft new or updated Supabase docs content for a feature or launch, grounded in product intent (Linear when available), a read of the actual code, and the docs style guide once one exists. Use when asked to write docs for a new feature, a product launch, or a Linear ticket that needs net-new content rather than a bug…
triage-issues
Triage GitHub issues in the googleapis/mcp-toolbox repo: propose the correct labels (type / priority / product / status), check for duplicates, verify a bug has enough info to act on, and draft a triage comment. Use whenever a maintainer asks you to triage, label, categorize, prioritize, or "look at" an issue (or a…
fix-ci
Check CI status, analyze test failures, auto-fix obvious issues or discuss with user.
postgresql-indexing
PostgreSQL indexing best practices for Prowler: index design, partial indexes, partitioned table indexing, EXPLAIN ANALYZE validation, concurrent operations, monitoring, and maintenance. Trigger: When creating or modifying PostgreSQL indexes, analyzing query performance with EXPLAIN, debugging slow queries, reviewing…
redis-inspect
Inspect Redis cache keys, values, and TTLs for debugging. Supports both main cache and system cache. Use for debugging cache issues, checking cached values, and monitoring cache state. Read-only by default.