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/openapi)<a href="https://agentmods.dev/rules/saynaai/sayna/openapi"><img src="https://agentmods.dev/badge/rules/saynaai/sayna/openapi/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/openapi"><img src="https://agentmods.dev/badge/rules/saynaai/sayna/openapi.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.05255 | $0.05255 |
| Opus 5.5 | $0.02102 | $0.02102 |
| Sonnet 5.5 | $0.01051 | $0.01051 |
| Haiku 4.5 | $0.00526 | $0.00526 |
Grade A, and why
openapi 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 — 790 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenAPI Documentation Guidelines
This document provides comprehensive guidelines for writing OpenAPI annotations in the Sayna Rust/Axum codebase using the utoipa crate.
Overview
Sayna uses utoipa (v5.3+, latest is v5.4) for OpenAPI 3.1 specification generation. All OpenAPI-related code is feature-gated behind the openapi feature flag to keep dependencies minimal in production builds.
Key Principles
- Feature-Gated: All OpenAPI code must be conditionally compiled with
#[cfg_attr(feature = "openapi", ...)] - Centralized Documentation: All paths, schemas, and tags are registered in
src/docs/openapi.rs - Complete Examples: Every field should have meaningful examples that reflect real-world usage
- Consistent Style: Follow established patterns for naming, descriptions, and error responses
- Type Safety: Leverage Rust's type system to ensure documentation matches implementation
Feature Flag Setup
Cargo.toml Configuration
[features]
openapi = [
"dep:utoipa",
]
[dependencies]
utoipa = { version = "5.3", optional = true, features = ["axum_extras"] }
# Optional: For more ergonomic route registration
# utoipa-axum = { version = "0.2", optional = true }
Optional: Enhanced Axum Integration
Consider adding utoipa-axum for more ergonomic route registration:
use utoipa_axum::{routes, router::OpenApiRouter};
let (router, api) = OpenApiRouter::new()
.routes(routes!(health_check, list_voices, speak_handler))
.split_for_parts();
Running with OpenAPI
# Run server with OpenAPI endpoints
cargo run --features openapi
# Generate OpenAPI spec to file
cargo run --features openapi -- openapi -o docs/openapi.yaml
# Generate JSON format
cargo run --features openapi -- openapi --format json -o docs/openapi.json
Schema Annotations
Basic Schema Definition
Use #[cfg_attr(feature = "openapi", derive(utoipa::ToSchema))] on all types exposed in the API:
use serde::{Deserialize, Serialize};
/// Health check response
#[derive(Debug, Serialize, Deserialize)]
#[cfg_attr(feature = "openapi", derive(utoipa::ToSchema))]
pub struct HealthResponse {
/// Server status
#[cfg_attr(feature = "openapi", schema(example = "OK"))]
pub status: String,
}
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 · 790 lines · 5,255 tokens per session scan A 1a2808a33674
openapi is a cursor rule published in the GitHub repository SaynaAI/sayna (314 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 5,255 tokens to every session, about $0.0210 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
api-property-optionality-hygiene
Fix ApiProperty/ApiPropertyOptional optionality mismatches in DTO files; use for scheduled batch fixes or DTO edits.
python
Python best practices and patterns for modern software development with Flask and SQLite.
django
Definitive guidelines for writing maintainable, performant, and secure Django applications, emphasizing modern best practices, clear code organization, and efficient patterns.
shared-libraries
Shared libraries - condition framework, inventory containers, file-backed DB, itinerary, references.
env-validation-gate
Env validation gate — every app with ≥1 required env var validates its contract at boot via Zod; raw process.env is banned outside the env module. Full pattern in .claude/skills/t2000-env-gate/.
go
Cursor rule "go" from supertokens/create-supertokens-app, covering go and examples.