301-framework-spring-boot

301-framework-spring-boot is a cursor rule for Cursor from alkoleft/platform-context-exporter. It costs 890 tokens per session, scanned A, original, MIT.

Development guidelines for Spring Boot applications, covering configuration, REST APIs, security, databases, and project structure. Spring Boot is a Java framework for building web services and applications.

In plain words
What is it for?
Use it when building or reviewing Spring Boot services, including REST endpoints, configuration profiles, security settings, database transactions, migrations, and API documentation.
Why use it?
It provides consistent choices for common application concerns, reducing mistakes in API behavior, configuration, authentication, database access, and deployment.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use it when building or reviewing Spring Boot services, including REST endpoints, configuration profiles, security settings, database transactions, migrations, and API documentation.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/alkoleft/platform-context-exporter/301-framework-spring-boot
Install

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.

Clone the repo
git clone --depth 1 https://github.com/alkoleft/platform-context-exporter

Made for: Cursor.

Wrote 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.

agentmods badge for 301-framework-spring-boot

README.md
[![agentmods](https://agentmods.dev/badge/rules/alkoleft/platform-context-exporter/301-framework-spring-boot/github.svg)](https://agentmods.dev/rules/alkoleft/platform-context-exporter/301-framework-spring-boot)
Your own site
<a href="https://agentmods.dev/rules/alkoleft/platform-context-exporter/301-framework-spring-boot"><img src="https://agentmods.dev/badge/rules/alkoleft/platform-context-exporter/301-framework-spring-boot/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.

agentmods 80×15 button for 301-framework-spring-boot

Your own site · 80×15
<a href="https://agentmods.dev/rules/alkoleft/platform-context-exporter/301-framework-spring-boot"><img src="https://agentmods.dev/badge/rules/alkoleft/platform-context-exporter/301-framework-spring-boot.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 890 This file is loaded in full into every session.
When invoked 890 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00890 $0.00890
Opus 5.5 $0.00356 $0.00356
Sonnet 5.5 $0.00178 $0.00178
Haiku 4.5 $0.00089 $0.00089

Measured 1mo ago against content hash 63d82eb79849, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

301-framework-spring-boot 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.

.cursor/rules/301-framework-spring-boot.mdc · 162 lines

How it starts

The opening of the file, as written. The whole thing — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Spring Boot Development Guidelines

Project Structure

Best Practices

Configuration

configuration_guidelines:

  • "Use configuration properties classes over @Value"
  • "Externalize configuration using application.yml"
  • "Use profiles for environment-specific settings"
  • "Follow the 12-factor app methodology"
  • "Use @ConfigurationProperties for type-safe configuration"

REST APIs

rest_guidelines:

  • "Follow REST maturity model"
  • "Use proper HTTP methods (GET, POST, PUT, DELETE)"
  • "Implement proper error handling with @ControllerAdvice"
  • "Use DTOs to control API response/request structure"
  • "Implement API versioning"
  • "Use proper HTTP status codes"
  • "Document APIs using OpenAPI/Swagger"

Security

security_guidelines:

  • "Enable HTTPS in production"
  • "Implement proper authentication and authorization"
  • "Use Spring Security for security concerns"
  • "Implement CORS properly"
  • "Follow OWASP security guidelines"
  • "Use security headers"
  • "Implement rate limiting"

Database

database_guidelines:

  • "Use Spring Data JDBC repositories when possible"
  • "Implement proper transaction management"
  • "Use connection pooling"
  • "Implement database migrations with Flyway/Liquibase"
  • "Implement proper indexing strategy"

Testing

testing_guidelines:

  • "Write unit tests for services and controllers"
  • "Use @SpringBootTest for integration tests"
  • "Implement test slices (@WebMvcTest, @DataJpaTest)"
  • "Use test containers for integration tests"
  • "Mock external services"
  • "Test configuration properties"

Performance

performance_guidelines:

  • "Use caching where appropriate"
  • "Implement connection pooling"
  • "Use async processing for long-running tasks"
  • "Implement proper logging levels"
  • "Use metrics and monitoring"
  • "Implement proper exception handling"

Code Examples

Configuration Properties
@ConfigurationProperties(prefix = "app")
@Validated
public class AppProperties {
    @NotNull
    private String apiKey;
    private int cacheTimeout;
    // getters and setters
}

Read the full file on GitHub · 162 lines

Changes

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.

  1. 1mo ago First seen · 162 lines · 890 tokens per session scan A 63d82eb79849

Subscribe to this mod's changes

301-framework-spring-boot is a cursor rule published in the GitHub repository alkoleft/platform-context-exporter (49 stars, last pushed 1y ago), licensed MIT. It adds 890 tokens to every session, about $0.0036 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.

Related

Other cursor rules, from other repositories

integrations

A development rule for building 1C integrations with external systems through HTTP APIs. It recommends first making and testing the requests in Python, then translating the working version into 1C’s BSL language.

Desko77/cursor-1c-skills · 24 tokens

1c-mdo-integrity

Rules for keeping 1C EDT MDO files structurally valid. MDO files describe configuration objects, and the rules cover unique identifiers and valid links between objects.

Desko77/cursor-1c-skills · 0 tokens

1c-skd-two-pass-preprocessing

A two-pass method for changing 1C report output before detailed records are combined into grouped totals. 1C's report system, СКД, builds reports by grouping and summarizing data.

Desko77/cursor-1c-skills · 0 tokens

1c-transactions-and-locks

Guidance for using transactions and controlled locks in 1C, where a transaction groups database changes so they can be accepted or cancelled together. It also explains the order in which locks should be taken when several operations share data.

Desko77/cursor-1c-skills · 0 tokens

1c-extension-patterns

A set of rules and examples for extending 1C configurations with BSL code and XML role metadata. 1C is an enterprise business-application platform, and BSL is its programming language.

Desko77/cursor-1c-skills · 0 tokens

testing-patterns

A set of rules and examples for testing 1C code with YaXUnit and Vanessa Automation. YaXUnit is used for unit tests of individual functions, while Vanessa Automation describes user scenarios as “given, when, then” steps.

Desko77/cursor-1c-skills · 0 tokens