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.
npx agentmods add skills/bdiasti/maestro-bundle-cli/jhipster-angularnpx skills add bdiasti/maestro-bundle-cli --skill jhipster-angulargit clone --depth 1 https://github.com/bdiasti/maestro-bundle-cliWrote 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/skills/bdiasti/maestro-bundle-cli/jhipster-angular)<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>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 | $0.00039 | $0.00963 |
| Opus 5 | $0.00019 | $0.00481 |
| Sonnet 5 | $0.00008 | $0.00193 |
| Haiku 4.5 | $0.00004 | $0.00096 |
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.
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
- Create services that aggregate data from multiple backends
- Handle partial service failures with fallback UI
- Add WebSocket real-time updates
- Build cross-service dashboards
- 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 }))
),
});
}
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.
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.
- 4d ago First seen · 140 lines · 39 tokens per session scan A 3c17261bfa7f
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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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.
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.
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.
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.
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…