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/hrygo/hotplex-legacy/hotplex-data-mgmt)<a href="https://agentmods.dev/skills/hrygo/hotplex-legacy/hotplex-data-mgmt"><img src="https://agentmods.dev/badge/skills/hrygo/hotplex-legacy/hotplex-data-mgmt.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.00057 | $0.01508 |
| Opus 5 | $0.00028 | $0.00754 |
| Sonnet 5 | $0.00011 | $0.00302 |
| Haiku 4.5 | $0.00006 | $0.00151 |
Grade D, and why
hotplex-data-mgmt scanned grade D 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 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sudo chown -R $(id -u):$(id -g) ~/.hotplex/instances/U0AHRCL1KCM Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
docker exec hotplex-01 rm -rf /home/hotplex/.hotplex/markers/* How it starts
The opening of the file, as written. The whole thing — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HotPlex Data Management
Manage persistent data including session markers, messages, and temporary files.
Critical: Working Directory
All docker compose commands MUST be executed from the compose directory.
COMPOSE_DIR="~/hotplex/docker/matrix"
Pattern: Always prefix docker compose commands with cd $COMPOSE_DIR &&:
cd ~/hotplex/docker/matrix && docker compose ps
Container Reference
| Container | Bot ID | Instance Path |
|---|---|---|
| hotplex-01 | U0AHRCL1KCM | ~/.hotplex/instances/U0AHRCL1KCM |
| hotplex-02 | U0AJVRH4YF6 | ~/.hotplex/instances/U0AJVRH4YF6 |
| hotplex-03 | U0AL7H8UU75 | ~/.hotplex/instances/U0AL7H8UU75 |
Session Markers
List Session Markers
# Host side (direct access)
ls -la ~/.hotplex/instances/U0AHRCL1KCM/markers/
# Container side
docker exec hotplex-01 ls -la /home/hotplex/.hotplex/markers/
Delete a Session Marker
# Host side
rm ~/.hotplex/instances/U0AHRCL1KCM/markers/<provider-session-id>
# Container side
docker exec hotplex-01 rm /home/hotplex/.hotplex/markers/<provider-session-id>
Delete All Markers for a Bot
docker exec hotplex-01 rm -rf /home/hotplex/.hotplex/markers/*
Clean Old Markers (24h+)
docker exec hotplex-01 find /home/hotplex/.hotplex/markers -type f -mtime +1 -delete
Message Storage
Check Database Size
docker exec hotplex-01 du -sh /home/hotplex/.hotplex/*.db
docker exec hotplex-01 ls -lh /home/hotplex/.hotplex/
Query Messages (SQLite)
# 按会话统计消息数
docker exec hotplex-01 sqlite3 /home/hotplex/.hotplex/chatapp_messages.db \
"SELECT session_id, COUNT(*) as msg_count FROM messages GROUP BY session_id ORDER BY msg_count DESC LIMIT 10"
# 按日期统计
docker exec hotplex-01 sqlite3 /home/hotplex/.hotplex/chatapp_messages.db \
"SELECT date(created_at) as date, COUNT(*) as count FROM messages GROUP BY date ORDER BY date DESC LIMIT 7"
# 查看表结构
docker exec hotplex-01 sqlite3 /home/hotplex/.hotplex/chatapp_messages.db ".schema"
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.
- 6d ago First seen · 221 lines · 57 tokens per session scan D 0b5caeeacb9b
hotplex-data-mgmt is a skill published in the GitHub repository hrygo/hotplex-legacy (11 stars, last pushed 4mo ago), licensed MIT. It adds 57 tokens to every session and 1,508 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it D with 2 findings (asks for root, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
sq
Guides use of the sq CLI to query SQL databases and tabular files with SLQ (sq's jq-like query language) or native SQL, manage sources, choose output formats, and run inspect, diff, and table commands. Use when the user mentions sq, SLQ, wrangling CSV/Excel/JSON/DB data, cross-source joins, or command-line data…
db
Database schema and query conventions for ThunderID. Use when changing schema scripts, defining SQL queries, updating store constants, or reviewing deployment-scoped persistence rules.
drt-analyze
Analyze DRT cluster health for a given time range. Reconstructs the operations timeline, checks CockroachDB metrics (availability, latency, storage, changefeeds, jobs, goroutines, admission control, LSM, KV prober) and logs for anomalies, correlates findings with disruptive operations to distinguish expected…
reduce-unoptimized-query-oracle
Reduce an unoptimized-query-oracle test failure log to the simplest possible reproduction case. Use when you have unoptimized-query-oracle.log files from a failed roachtest and need to find the minimal SQL to reproduce the bug.
redux-to-swr
Migrate React components from Redux + Saga to SWR hooks. Use when converting data fetching from Redux store (reducers, sagas, selectors, connect HOC) to SWR-based hooks in CockroachDB DB Console or cluster-ui.
mma-investigator
Expert system for investigating MMA (Multi-Metric Allocator) behavior on CockroachDB clusters. Helps oncall engineers diagnose load imbalances, understand rebalancing decisions, and identify why MMA did or didn't act.