jhipster-angular

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

A JHipster Angular skill for building the frontend gateway of a microservice application, where one gateway connects the browser to several backend services.

In plain words
What is it for?
Use it to build cross-service dashboards, create gateway services, handle partial failures, customize components, or add WebSocket updates.
Why use it?
It helps combine data from multiple services and keep the interface usable when some services fail or when updates need to arrive in real time.

Skill for Claude CodeCodex

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 skills/bdiasti/maestro-bundle-cli/jhipster-angular
Any agent
npx skills add bdiasti/maestro-bundle-cli --skill jhipster-angular
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-angular

README.md
[![agentmods](https://agentmods.dev/badge/skills/bdiasti/maestro-bundle-cli/jhipster-angular.svg)](https://agentmods.dev/skills/bdiasti/maestro-bundle-cli/jhipster-angular)
Your own site
<a href="https://agentmods.dev/skills/bdiasti/maestro-bundle-cli/jhipster-angular"><img src="https://agentmods.dev/badge/skills/bdiasti/maestro-bundle-cli/jhipster-angular.svg" alt="Measured on agentmods" height="20"></a>
Per session 39 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 963 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00039 $0.00963
Opus 5 $0.00019 $0.00481
Sonnet 5 $0.00008 $0.00193
Haiku 4.5 $0.00004 $0.00096

Measured 4d ago against content hash 3c17261bfa7f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

jhipster-angular 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 4d 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-angular/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 Angular -- Microservices

Develop the Angular frontend hosted in the Gateway, which transparently consumes multiple microservices through the Gateway's routing.

When to Use

  • When creating screens that aggregate data from multiple services
  • When building dashboards with data from different microservices
  • When handling partial service failures gracefully in the UI
  • When adding WebSocket real-time features via the Gateway

Available Operations

  1. Create services that aggregate data from multiple backends
  2. Handle partial service failures with fallback UI
  3. Add WebSocket real-time updates
  4. Build cross-service dashboards
  5. Customize entity components from different services

Multi-Step Workflow

Step 1: Understand the Architecture

Browser --> Gateway:8080/api/demands --> demand-service:8081/api/demands
Browser --> Gateway:8080/api/agents  --> agent-service:8082/api/agents

The Angular app lives in the Gateway. From Angular's perspective, everything is a single API.

Step 2: Create Services That Aggregate Data

// dashboard.service.ts -- aggregates data from multiple services (via gateway)
@Injectable({ providedIn: 'root' })
export class DashboardService {
  constructor(
    private demandService: DemandService,
    private agentService: AgentService,
    private trackingService: TrackingService,
  ) {}

  getMetrics(): Observable<DashboardMetrics> {
    return forkJoin({
      activeDemands: this.demandService.countByStatus('IN_PROGRESS'),
      activeAgents: this.agentService.countByStatus('BUSY'),
      completedToday: this.trackingService.getCompletedToday(),
      complianceRate: this.trackingService.getComplianceRate(),
    });
  }
}

Step 3: Handle Partial Service Failures

getMetrics(): Observable<DashboardMetrics> {
  return forkJoin({
    activeDemands: this.demandService.countByStatus('IN_PROGRESS').pipe(
      catchError(() => of({ count: -1 }))  // -1 = unavailable
    ),
    activeAgents: this.agentService.countByStatus('BUSY').pipe(
      catchError(() => of({ count: -1 }))
    ),
  });
}

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. 4d ago First seen · 140 lines · 39 tokens per session scan A 3c17261bfa7f

Subscribe to this mod's changes

jhipster-angular is a skill published in the GitHub repository bdiasti/maestro-bundle-cli (21 stars, last pushed 5mo ago), licensed MIT. It adds 39 tokens to every session and 963 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

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens