jhipster-entities

jhipster-entities is a skill for Claude Code, Codex from bdiasti/maestro-bundle-cli. It costs 43 tokens per session (911 once invoked), scanned A, original, MIT.

A guide for defining and generating data entities in JHipster microservices. It explains how entities belong to individual services and how services refer to each other's records by ID instead of using shared database links.

In plain words
What is it for?
Use it to define entities with JDL, assign them to services, model cross-service references, generate code, fetch related data with Feign, and create shared DTOs.
Why use it?
It helps prevent incorrect database relationships between services and gives a consistent way to generate each service's code and shared data formats.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to define entities with JDL, assign them to services, model cross-service references, generate code, fetch related data with Feign, and create shared DTOs.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/bdiasti/maestro-bundle-cli/jhipster-entities
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.

Any agent
npx skills add bdiasti/maestro-bundle-cli --skill jhipster-entities
Clone the repo
git clone --depth 1 https://github.com/bdiasti/maestro-bundle-cli

Made for: Claude Code, Codex.

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 jhipster-entities

README.md
[![agentmods](https://agentmods.dev/badge/skills/bdiasti/maestro-bundle-cli/jhipster-entities/github.svg)](https://agentmods.dev/skills/bdiasti/maestro-bundle-cli/jhipster-entities)
Your own site
<a href="https://agentmods.dev/skills/bdiasti/maestro-bundle-cli/jhipster-entities"><img src="https://agentmods.dev/badge/skills/bdiasti/maestro-bundle-cli/jhipster-entities/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 jhipster-entities

Your own site · 80×15
<a href="https://agentmods.dev/skills/bdiasti/maestro-bundle-cli/jhipster-entities"><img src="https://agentmods.dev/badge/skills/bdiasti/maestro-bundle-cli/jhipster-entities.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 43 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 911 The whole file, excluding the scripts and references it only reads on demand.
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.00043 $0.00911
Opus 5 $0.00022 $0.00456
Sonnet 5 $0.00009 $0.00182
Haiku 4.5 $0.00004 $0.00091

Measured 9d ago against content hash a3adc29bc9bf, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

jhipster-entities 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 9d 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.

templates/bundle-jhipster-microservices/skills/jhipster-entities/SKILL.md · 140 lines

How it starts

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

JHipster Entities -- Microservices

Create and manage JHipster entities in a microservices architecture where entities belong to specific services and cross-service relationships use IDs instead of foreign keys.

When to Use

  • When creating entities assigned to specific microservices
  • When defining cross-service relationships (by ID, not FK)
  • When generating code with jhipster import-jdl for microservices
  • When implementing Feign-based data fetching across services

Available Operations

  1. Define entities with microservice assignment in JDL
  2. Handle cross-service references with ID fields
  3. Generate code per microservice
  4. Implement Feign-based data aggregation
  5. Create shared DTOs for inter-service communication

Multi-Step Workflow

Step 1: Define Entities with Microservice Assignment

/* demand-service entities */
entity Demand {
    description TextBlob required
    status DemandStatus required
    priority Priority required
    createdAt Instant required
}

entity Task {
    description String required maxlength(500)
    status TaskStatus required
    agentId Long             // ID from another service, not FK
    branchName String
}

relationship OneToMany {
    Demand{tasks} to Task{demand required}
}

microservice Demand, Task with demandService

/* agent-service entities */
entity Agent {
    name String required
    type AgentType required
    status AgentStatus required
    worktreePath String
}

entity AgentTeam {
    demandId Long required   // ID from another service, not FK
}

relationship ManyToMany {
    AgentTeam{agents} to Agent
}

microservice Agent, AgentTeam with agentService

Step 2: Generate Code

# Generate all microservices from JDL
jhipster import-jdl jhipster-jdl.jdl

# Verify generated files per service
ls demand-service/src/main/java/*/domain/
ls agent-service/src/main/java/*/domain/

Step 3: Implement Cross-Service Data Fetching

// In demand-service -- Task stores only agentId
@Entity
public class Task {
    private Long agentId;  // Just the ID, not the Agent entity
}

// In demand-service -- fetch Agent data via Feign
@Service
public class DemandServiceImpl {
    private final AgentServiceClient agentClient;

    public TaskDetailDTO getTaskDetail(Long taskId) {
        Task task = taskRepository.findById(taskId).orElseThrow();
        AgentDTO agent = agentClient.getAgent(task.getAgentId()); // Feign call
        return new TaskDetailDTO(task, agent);
    }
}

Read the full file on GitHub · 140 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 9d ago First seen · 140 lines · 43 tokens per session scan A a3adc29bc9bf

Subscribe to this mod's changes

jhipster-entities is a skill published in the GitHub repository bdiasti/maestro-bundle-cli (21 stars, last pushed 5mo ago), licensed MIT. It adds 43 tokens to every session and 911 once invoked, about $0.0002 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-08-30.

Related

Other skills, from other repositories

event-store-design

Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.

wshobson/agents · 33 tokens

convex-explain-app

Explain an existing Convex app — data model + relationships, public vs internal functions, auth/ownership model, components, a request→data flow — read from the schema and function surface. Read-only.

openclaw/clawhub · 47 tokens

platform-custom-field-generate

Use this skill when users need to create, generate, or validate Salesforce Custom Field metadata. Trigger when users mention custom fields, field types, Roll-up Summary fields, Master-Detail relationships, Lookup relationships, formula fields, picklists, dependent (controlling) picklists, referencing a value set from…

forcedotcom/sf-skills · 194 tokens

openloomi-api

OpenLoomi ships a local-first HTTP API served from the desktop app (port 3414, fallback 3515). All auth, Memory, AI, RAG, Loop, and Audit data live in a local SQLite database — your data stays on your machine and the OpenLoomi app is the source of truth. The only externally-routed auth path is the Composio OAuth…

melandlabs/openloomi · 106 tokens

nornicdb-grpc

Drive NornicDB over gRPC — the Qdrant-compatible surface (Collections, Points, Snapshots) plus the additive NornicSearch service. Use when ingesting via Qdrant SDKs, migrating from Qdrant, or running hybrid text+vector search from a non-Bolt client. Covers connection, RPC catalog, collection→database mapping…

orneryd/NornicDB · 98 tokens

field-service-sobject-create-configure

Headless 360 REST API deployment step for creating sObject records. Handles describe-based field discovery, required-field derivation, entity-relationship ordering, and composite graph transactions. Use this skill when a designer skill (or a user directly) needs to create sObject records after design confirmation…

forcedotcom/sf-skills · 74 tokens