cursor-rules-java

A curated collection of prompts and skills for software teams building Java enterprise applications. It includes guidance for agile work, architecture decisions, tooling, and other software-development tasks.

In plain words
What is it for?
Use it to define epics, features, and user stories, document architecture decisions, and support everyday Java enterprise development workflows.
Why use it?
It provides reusable guidance for common Java development and delivery activities, reducing the need to write each instruction from scratch.

Plugin for Claude Code

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.

agentmods
npx agentmods add plugins/jabrena/plinth/marketplace
Claude Code
/plugin marketplace add jabrena/plinth
Clone the repo
git clone --depth 1 https://github.com/jabrena/plinth

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

cursor-rules-java 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.

.claude-plugin/marketplace.json · 383 lines

How it starts

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

{
    "name": "cursor-rules-java",
    "owner": {
        "name": "Juan Antonio Breña Moral",
        "email": "[email protected]"
    },
    "metadata": {
        "description": "Curated collection of System prompts & Skills for modern SDLC that help software engineers and pipelines in their daily work for Java Enterprise development.",
        "homepage": "https://jabrena.github.io/cursor-rules-java/",
        "repository": "https://github.com/jabrena/cursor-rules-java",
        "version": "0.14.0-SNAPSHOT",
        "license": "Apache-2.0"
    },
    "plugins": [
        {
            "name": "012-agile-epic",
            "source": "./skills/012-agile-epic",
            "description": "Guides the creation of agile epics with comprehensive definition including business value, success criteria, and breakdown into user stories. Use when the user wants to create an agile epic, define large bodies of work, break down features into user stories, or document strategic initiatives.",
            "version": "0.14.0-SNAPSHOT"
        },
        {
            "name": "013-agile-feature",
            "source": "./skills/013-agile-feature",
            "description": "Guides the creation of detailed agile feature documentation from an existing epic. Use when the user wants to split an epic into feature files, derive features with scope and acceptance criteria, or plan feature documentation for stakeholders or engineering.",
            "version": "0.14.0-SNAPSHOT"
        },
        {
            "name": "014-agile-user-story",
            "source": "./skills/014-agile-user-story",
            "description": "Guides the creation of agile user stories and Gherkin feature files. Use when the user wants to create a user story, write acceptance criteria, define Gherkin scenarios, or author BDD feature files.",
            "version": "0.14.0-SNAPSHOT"
        },
        {
            "name": "021-tooling-github",
            "source": "./skills/021-tooling-github",
            

Read the full file on GitHub · 383 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. yesterday First seen · 383 lines scan A f2ca278974a4

Subscribe to this mod's changes

cursor-rules-java is a plugin published in the GitHub repository jabrena/plinth (435 stars, last pushed today), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories