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-servicesnpx skills add readysettech/rdst --skill rdst-servicesgit 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/skills/readysettech/rdst/rdst-services)<a href="https://agentmods.dev/skills/readysettech/rdst/rdst-services"><img src="https://agentmods.dev/badge/skills/readysettech/rdst/rdst-services.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.00000 | $0.03194 |
| Opus 5 | $0.00000 | $0.01597 |
| Sonnet 5 | $0.00000 | $0.00639 |
| Haiku 4.5 | $0.00000 | $0.00319 |
Grade A, and why
rdst-services 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 5d 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 — 551 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RDST Service Creation Guide
This skill provides guidance for creating new services in rdst/lib/services/.
Why Services Exist
Services are the single source of truth for business logic shared between:
- CLI commands - via
asyncio.run()bridge with Renderer for terminal output - Web API - via native async with SSE (Server-Sent Events) streaming
- MCP server - via async interface for Claude Code integration
This architecture ensures:
- No logic duplication between CLI and web
- Consistent behavior across all interfaces
- Testable, isolated business logic
- Type-safe event contracts
Service Patterns
RDST uses two primary patterns:
1. Async Generator Services (Streaming)
Use for operations that:
- Take time and benefit from progress updates
- Need to stream results incrementally
- May require user interaction mid-execution
# my_service.py
from typing import AsyncGenerator
from .types import MyEvent, MyInput, MyOptions
class MyService:
"""Stateless service for [description]."""
def __init__(self) -> None:
"""Initialize (no constructor parameters - stateless)."""
pass
async def do_thing(
self,
input: MyInput,
options: MyOptions,
) -> AsyncGenerator[MyEvent, None]:
"""Execute operation and yield events.
Yields:
MyStatusEvent: Progress updates
MyResultEvent: Final results
MyErrorEvent: On failure
"""
try:
yield MyStatusEvent(type="status", message="Starting...")
# Do work...
result = await self._perform_work(input)
yield MyResultEvent(type="result", data=result)
except Exception as e:
yield MyErrorEvent(type="error", message=str(e))
2. Synchronous Services (Return-based)
Use for operations that:
- Complete quickly
- Don't need streaming feedback
- Return structured results
# my_service.py
from .types import MyResult, MyInput
class MyService:
"""Stateless service for [description]."""
def __init__(self) -> None:
pass
def get_status(self) -> MyResult:
"""Check status and return result."""
# Do work...
return MyResult(
success=True,
data={"key": "value"}
)
def perform_action(self, input: MyInput) -> MyResult:
"""Perform action and return result."""
try:
# Do work...
return MyResult(success=True, message="Done")
except Exception as e:
return MyResult(success=False, error=str(e))
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.
- 5d ago First seen · 551 lines · 0 tokens per session scan A 91eda84930b0
rdst-services is a skill published in the GitHub repository readysettech/rdst (12 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,194 tokens. 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…