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.
git clone --depth 1 https://github.com/SaynaAI/saynaWrote 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/rules/saynaai/sayna/core)<a href="https://agentmods.dev/rules/saynaai/sayna/core"><img src="https://agentmods.dev/badge/rules/saynaai/sayna/core/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/saynaai/sayna/core"><img src="https://agentmods.dev/badge/rules/saynaai/sayna/core.svg" alt="Reviewed on agentmods" width="80" 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.01582 | $0.01582 |
| Opus 5.5 | $0.00633 | $0.00633 |
| Sonnet 5.5 | $0.00316 | $0.00316 |
| Haiku 4.5 | $0.00158 | $0.00158 |
Grade A, and why
core 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 1mo 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sayna Core Module
This Rust Axum project is a unified STT, TTS server that handles real-time WebSocket APIs for STT and TTS providers like Deepgram, ElevenLabs, Google, Microsoft Azure, Cartesia, and others into one unified WebSocket API that abstracts away provider-specific details.
The main business logic is inside src/core/, which uses trait-based abstraction to have unified higher-level implementations of TTS and STT separated into dedicated folders.
STT Base Abstraction (src/core/stt/base.rs)
The BaseSTT trait defines the interface for all STT providers:
Required Methods
| Method | Signature | Description |
|---|---|---|
new |
fn new(config: STTConfig) -> Result<Self, STTError> |
Create a new instance with STT configuration |
connect |
async fn connect(&mut self) -> Result<(), STTError> |
Initiate connection to STT provider |
disconnect |
async fn disconnect(&mut self) -> Result<(), STTError> |
Disconnect from provider |
is_ready |
fn is_ready(&self) -> bool |
Check if connection is ready |
send_audio |
async fn send_audio(&mut self, audio_data: Vec<u8>) -> Result<(), STTError> |
Send audio bytes for transcription |
on_result |
async fn on_result(&mut self, callback: STTResultCallback) -> Result<(), STTError> |
Register transcription result callback |
on_error |
async fn on_error(&mut self, callback: STTErrorCallback) -> Result<(), STTError> |
Register error callback for streaming errors |
get_config |
fn get_config(&self) -> Option<&STTConfig> |
Get current configuration |
update_config |
async fn update_config(&mut self, config: STTConfig) -> Result<(), STTError> |
Update configuration while connected |
get_provider_info |
fn get_provider_info(&self) -> &'static str |
Get provider-specific information |
STTResult Type
pub struct STTResult {
pub transcript: String, // The transcribed text
pub is_final: bool, // Whether this is a final result
pub is_speech_final: bool, // Whether speech segment ended
pub confidence: f32, // Confidence score (0.0 to 1.0)
}
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.
- 1mo ago First seen · 131 lines · 1,582 tokens per session scan A cd195b9d747e
core is a cursor rule published in the GitHub repository SaynaAI/sayna (314 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 1,582 tokens to every session, about $0.0063 per session on Opus 5.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 cursor rules, from other repositories
rust
Rules for writing Rust services at PostHog. Focuses on writing async Rust with Tokio and encoding general Rust best practices from the Rust book and docs.
actix-web
Definitive guidelines for building high-performance, maintainable, and secure web applications with actix-web 4, focusing on modern Rust best practices.
rocket
Definitive guidelines for building robust, performant, and maintainable backend services with Rocket 0.5+, focusing on modern Rust async patterns, API design, and testing.
rust-hexagonal
Règles Rust Architecture Hexagonale avec gRPC (tonic).
axum
Cursor rule "axum" from tyrchen/cursor-rust-rules, covering 🌐 axum web framework standards, 🏗️ axum application architecture, 🎯 axum version and setup, axum 0.8+ requirements and 📦 axum dependencies.
protobuf-grpc
Cursor rule "protobuf-grpc" from tyrchen/cursor-rust-rules, covering 🛜 rust protobuf & grpc standards, 🔍 protobuf & grpc design strategy, 🎯 protobuf & grpc framework requirements, prost/tonic configuration and 📦 protobuf & grpc dependencies.