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 instructions/readysettech/rdst/claude-mdgit clone --depth 1 https://github.com/readysettech/rdstWrote 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/instructions/readysettech/rdst/claude-md)<a href="https://agentmods.dev/instructions/readysettech/rdst/claude-md"><img src="https://agentmods.dev/badge/instructions/readysettech/rdst/claude-md.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 | $0.02112 | $0.02112 |
| Opus 5 | $0.01056 | $0.01056 |
| Sonnet 5 | $0.00422 | $0.00422 |
| Haiku 4.5 | $0.00211 | $0.00211 |
Grade A, and why
rdst CLAUDE.md 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 4d 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 — 270 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RDST - Readyset Data and SQL Toolkit
Quick Reference
Root directory: readyset/rdst/ (NOT cloud/cloud_agent/ - that's deprecated)
Entry point: rdst.py - main CLI
Architecture: See ARCHITECTURE.md for the current features/ + shared/ ownership model.
Running RDST
Local Development (Recommended)
# Run directly from source - no installation needed
python3 rdst.py <command>
# Or with uv (if using uv for dependency management)
uv run rdst.py <command>
Installation Options
# Using uv (recommended - doesn't pollute system Python)
uv pip install -e .
# Using pip (installs to system/virtualenv)
pip install -e .
# The -e flag means "editable" - changes to source are reflected immediately
After installation, you can run rdst <command> directly instead of python3 rdst.py <command>.
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/manage semantic layer |
rdst scan ./path |
Scan codebase for ORM queries |
rdst query list |
View saved queries |
rdst query run <names> |
Benchmark/load test queries |
rdst help "question" |
Documentation lookup |
rdst claude add |
Register MCP server with Claude Code |
Configuration
- Config file:
~/.rdst/config.toml - Query registry:
~/.rdst/queries.toml - Passwords: Never stored - use
password_envto reference environment variables
Testing
# Run all tests
pytest tests/
# Run specific test file
pytest tests/ask_experimental/test_ask3_engine/test_engine.py -v
# Quick validation
python3 rdst.py version
python3 rdst.py --help
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.
- 4d ago First seen · 270 lines · 2,112 tokens per session scan A 7c556006b06e
rdst CLAUDE.md is an instructions file published in the GitHub repository readysettech/rdst (11 stars, last pushed 23d ago), licensed MIT. It adds 2,112 tokens to every session, about $0.0106 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.