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 skills/readysettech/rdst/rdst-python-toolkitnpx skills add readysettech/rdst --skill rdst-python-toolkitgit clone --depth 1 https://github.com/readysettech/rdstWhat 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.00087 | $0.02384 |
| Opus 5 | $0.00044 | $0.01192 |
| Sonnet 5 | $0.00017 | $0.00477 |
| Haiku 4.5 | $0.00009 | $0.00238 |
Grade A, and why
rdst-python-toolkit 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 2d 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 — 368 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RDST - Readyset Data and SQL Toolkit
Python CLI & API for database diagnostics, query optimization, and NL-to-SQL.
Stack: Python 3.11+, Rich (terminal UI), FastAPI (web API), Typer (CLI)
Project Structure
rdst/
├── rdst.py # CLI entry point (argparse)
├── mcp_server.py # MCP server for Claude Code integration
├── lib/
│ ├── cli/ # Command implementations
│ ├── api/ # FastAPI routes
│ ├── services/ # Event-driven async services
│ ├── functions/ # Core business logic (shared)
│ ├── ui/ # Rich terminal components
│ ├── llm_manager/ # LLM provider abstraction
│ ├── engines/ask3/ # NL-to-SQL engine
│ └── prompts/ # LLM prompt templates
└── tests/ # Test cases
Running RDST
python3 rdst.py <command> # Direct run
uv run rdst.py <command> # With uv
rdst <command> # After pip install -e .
Key Commands
| Command | Description |
|---|---|
rdst init |
First-time setup wizard |
rdst configure |
Manage database targets |
rdst analyze -q "SQL" |
Analyze query performance |
rdst top --target X |
Monitor slow queries |
rdst ask "question" |
Natural language to SQL |
rdst schema show |
View semantic layer |
rdst query list |
View saved queries |
CRITICAL: Rich Component Imports
NEVER import Rich directly. Always use lib.ui:
# WRONG - direct Rich imports
from rich.console import Group
from rich.text import Text
from rich.tree import Tree
from rich.panel import Panel
# CORRECT - import from lib.ui
from lib.ui import Group, Text, Tree, Spinner, Live
from lib.ui import StyledPanel, StyledTable, MessagePanel
from lib.ui import get_console, StyleTokens, Icons
If a Rich component is needed but not exported, add it to lib/ui/components.py and lib/ui/__init__.py.
UI Design System (lib/ui/)
Atomic Design Hierarchy
| Layer | Purpose | Examples |
|---|---|---|
| Atoms | Base building blocks | StyledPanel, StyledTable |
| Molecules | Composable units | MessagePanel, DataTable, StatusLine |
| Organisms | Domain-specific | QueryPanel, TopQueryTable, AnalysisHeader |
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.
- 2d ago First seen · 368 lines · 87 tokens per session scan A 982bcf151d58
rdst-python-toolkit is a skill published in the GitHub repository readysettech/rdst (11 stars, last pushed 21d ago), licensed MIT. It adds 87 tokens to every session and 2,384 once invoked, about $0.0004 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…