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/sunra-ai/sunra-clientsWrote 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/sunra-ai/sunra-clients/java-sdk)<a href="https://agentmods.dev/rules/sunra-ai/sunra-clients/java-sdk"><img src="https://agentmods.dev/badge/rules/sunra-ai/sunra-clients/java-sdk.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.02517 | $0.02517 |
| Opus 5 | $0.01259 | $0.01259 |
| Sonnet 5 | $0.00503 | $0.00503 |
| Haiku 4.5 | $0.00252 | $0.00252 |
Grade A, and why
java-sdk 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 yesterday.
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 — 374 lines — stays where its author put it; the contents beside it link to each section on GitHub.
description: This document defines the role and responsibilities of a Java SDK Developer for the Sunra Clients project. The Java SDK provides synchronous, asynchronous, and Kotlin-compatible client libraries for interacting with Sunra.ai services. globs: alwaysApply: false
Sunra Clients - Java SDK Developer Role Document
Overview
This document defines the role and responsibilities of a Java SDK Developer for the Sunra Clients project. The Java SDK provides synchronous, asynchronous, and Kotlin-compatible client libraries for interacting with Sunra.ai services.
Project Structure
The Java SDK consists of three main modules:
- client/: Main synchronous Java client
- client-async/: Asynchronous Java client implementation
- client-kotlin/: Kotlin-specific client with coroutines support
Development Guidelines
1. Code Style and Standards
Java Style Guide
- Follow Google Java Style Guide conventions
- Use 2 spaces for indentation (as per user preference)
- Maximum line length: 120 characters
- Use PascalCase for class names:
SunraClient,QueueClient - Use camelCase for method names:
submitRequest,getStatus - Use UPPER_SNAKE_CASE for constants:
DEFAULT_TIMEOUT,MAX_RETRIES
Kotlin Style Guide
- Follow Kotlin Coding Conventions
- Use 2 spaces for indentation
- Prefer data classes for DTOs and configuration objects
- Use nullable types appropriately:
String?instead ofOptional<String> - Leverage coroutines for asynchronous operations
2. Architecture Patterns
Client Architecture
// Synchronous client pattern
public class SunraClient {
private final HttpClient httpClient;
private final CredentialsResolver credentialsResolver;
private final QueueClient queueClient;
public static SunraClient withEnvCredentials() {
return new SunraClientImpl(CredentialsResolver.fromEnvironment());
}
}
// Asynchronous client pattern
public class AsyncSunraClient {
public CompletableFuture<Output> subscribe(String endpointId, SubscribeOptions options) {
return CompletableFuture.supplyAsync(() -> {
// Implementation
});
}
}
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.
- yesterday First seen · 374 lines · 2,517 tokens per session scan A 3ac0be677542
java-sdk is a cursor rule published in the GitHub repository sunra-ai/sunra-clients (7 stars, last pushed 8d ago), licensed Apache-2.0. It adds 2,517 tokens to every session, about $0.0126 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-09-04.
Other cursor rules, from other repositories
drizzle-patterns
Drizzle ORM patterns and database conventions.
backend
Backend Java — Spring Boot controllers/services, JUnit controller tests, MakeMe. Read this first for any backend work.
java-import-fqn
A Java code rule that requires using imports and short class names when class names do not conflict. Fully qualified names remain allowed for documented exceptions such as naming conflicts and certain strings.
springboot-jpa-best-practices
A set of Chinese-language rules for structuring Java Spring Boot applications that use JPA, a library for database access.
component-parameter-key-no-dot
A naming rule for Java code parameters marked with @ComponentParameter. Their keys must be flat names using letters, numbers, and underscores; dots are not allowed.
java-17-development-standards
Java-specific development standards following Effective Java, Google Java Style Guide, and modern Java 17 LTS best practices.