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/rayvise/rayvise-cliWrote 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/rayvise/rayvise-cli/rayvise-project)<a href="https://agentmods.dev/rules/rayvise/rayvise-cli/rayvise-project"><img src="https://agentmods.dev/badge/rules/rayvise/rayvise-cli/rayvise-project/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/rayvise/rayvise-cli/rayvise-project"><img src="https://agentmods.dev/badge/rules/rayvise/rayvise-cli/rayvise-project.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.00915 | $0.00915 |
| Opus 5.5 | $0.00366 | $0.00366 |
| Sonnet 5.5 | $0.00183 | $0.00183 |
| Haiku 4.5 | $0.00092 | $0.00092 |
Grade A, and why
rayvise-project 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
rayvise-cli Project Context
Architecture Overview
CLI Tool: Cobra-based CLI for generating AI-optimized prompts via OpenRouter API with automatic project context awareness
Key Packages:
cmd/- Cobra commands (root, generate, interactive)internal/config/- Viper config + model registryinternal/llm/- OpenRouter client with streaminginternal/prompts/- Prompt templates + storeinternal/projectcontext/- Project context detection and loadinginternal/clipboard/- Cross-platform clipboard opspkg/types/- Shared types
Core Concepts
Output Lengths: Control response size via max_tokens + system prompt directives
short: 300 tokens, concise promptsmedium: 800 tokens, balanced detaillong: 1500 tokens, comprehensive
Model Resolution: Custom models → DefaultModels → treat as OpenRouter ID
Config Hierarchy: CLI flags → env vars (RAYVISE_*) → ~/.rayvise/config.yaml → defaults
Streaming: SSE parsing for interactive mode, non-streaming for generate command
Project Context Awareness: Automatically discovers and loads context from .cursor/rules/, CLAUDE.md, or AGENTS.md files (in priority order). Context is injected into the system prompt via {{.Context}} template variable, allowing generated prompts to be aware of project conventions and architecture.
Code Patterns
Error Handling:
// Network errors: retry once
if err != nil || resp.StatusCode >= 500 {
time.Sleep(1 * time.Second)
resp, err = client.Do(req)
}
// User-facing errors: clear, actionable
return fmt.Errorf("API key not found. Set RAYVISE_API_KEY or add to config.yaml")
Config Access:
cfg := config.GetConfig()
apiKey := cfg.GetAPIKey() // Falls back to env var
model := cfg.GetDefaultModel() // Falls back to "cerebras-llama-8b"
Prompt Rendering:
store, _ := prompts.NewStore()
systemPrompt, _ := store.Render("metaprompt", types.OutputLengthMedium)
// Template {{.LengthDirective}} auto-replaced
// Template {{.Context}} auto-replaced with project context (if found)
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 · 116 lines · 915 tokens per session scan A 143cb431466b
rayvise-project is a cursor rule published in the GitHub repository rayvise/rayvise-cli (8 stars, last pushed 5mo ago), licensed MIT. It adds 915 tokens to every session, about $0.0037 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-31.
Other cursor rules, from other repositories
code-style
Formatting, lint, comments language.
hatch3r-go-patterns
Go 1.23+ conventions covering modules, error wrapping, context propagation, generics, testing with table-driven tests, and the standard library net/http + log/slog.
go
Go patterns: error wrapping, goroutines, interfaces.
coding-style
Go coding standards for order-service.
Go安全规范
Go coding rules for safer handling of secrets, input, environment variables, and operations that may wait. They also specify using gosec, a tool that scans Go code for common security issues.
go-coding-standards
You are an expert in Go, microservices architecture, and clean backend development practices. Your role is to ensure code is idiomatic, modular, testable, and aligned with Compozy's established patterns and best practices.