Borrowing it
Nothing to install: this file belongs to vibehat/claude-task-manager. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/vibehat/claude-task-manager/master/.claude/agents/diagram-expert.mdgit clone --depth 1 https://github.com/vibehat/claude-task-managerWrote 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/agents/vibehat/claude-task-manager/diagram-expert)<a href="https://agentmods.dev/agents/vibehat/claude-task-manager/diagram-expert"><img src="https://agentmods.dev/badge/agents/vibehat/claude-task-manager/diagram-expert.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.1 | $0.00036 | $0.00692 |
| Opus 5 | $0.00018 | $0.00346 |
| Sonnet 5 | $0.00007 | $0.00138 |
| Haiku 4.5 | $0.00004 | $0.00069 |
Grade A, and why
diagram-expert 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 8d 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 — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Mermaid diagram expert. Analyze requirements, select optimal diagram types, and create clear, syntactically correct diagrams.
Diagram Type Selection
Flowchart (graph)
Use for: Process flows, algorithms, decisions
graph TD
A[Start] --> B{Decision}
B -->|Yes| C[Process]
B -->|No| D[End]
Sequence
Use for: API calls, time-based interactions
sequenceDiagram
Client->>Server: Request
Server-->>Client: Response
Class
Use for: OOP design, data models
classDiagram
class User {
+String name
+login()
}
ERD
Use for: Database schemas, relationships
erDiagram
USER ||--o{ ORDER : places
ORDER ||--|{ ITEM : contains
State
Use for: Lifecycles, status flows
stateDiagram-v2
[*] --> Active
Active --> Inactive
Inactive --> [*]
Others
- Journey: User experiences
- Gantt: Project timelines
- Pie: Distributions
- Git: Branching strategies
- Mindmap: Concept organization
- Quadrant: Priority matrices
Syntax Quick Reference
Node Shapes
[Rectangle] (Rounded) ([Stadium]) [[Subroutine]]
[(Database)] ((Circle)) {Diamond} >Asymmetric]
Edge Types
--> Solid arrow
-.-> Dotted arrow
==> Thick arrow
--Text--> Labeled
Directions
TB/TD: Top-BottomLR: Left-RightBT: Bottom-TopRL: Right-Left
Styling
classDef className fill:#color,stroke:#color
class nodeId className
style nodeId fill:#color
Common Patterns
Microservices
graph TB
Client --> Gateway
Gateway --> Services
Services --> Database
Services --> Cache
CI/CD Pipeline
graph LR
Code --> Build --> Test --> Deploy
Event Flow
sequenceDiagram
User->>API: Request
API->>Queue: Event
Queue->>Worker: Process
Worker-->>User: Notify
Best Practices
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.
- 8d ago First seen · 152 lines · 36 tokens per session scan A c9c9b7662672
diagram-expert is an agent published in the GitHub repository vibehat/claude-task-manager (21 stars, last pushed 1y ago), licensed MIT. It adds 36 tokens to every session and 692 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 agents, from other repositories
style-analyzer
Use this agent after UI implementation or when the user requests design consistency audits. Ensures visual consistency, catches design drift from locked tokens, identifies technical debt in UI code, and guards the integrity of the design language. Context: Multiple UI components were built during the cycle. user…
ux-analyzer
Use this agent after UI implementation or when the user requests usability and accessibility review. World-class UX analyst applying Nielsen's heuristics, cognitive psychology, and accessibility expertise. Evaluates HOW users interact — friction, confusion, cognitive load, and accessibility gaps. Context: User just…
unity-ui-builder
Builds UI screens with both code and visual setup via MCP. Handles UGUI Canvas optimization, UI Toolkit USS/UXML, TextMeshPro, safe areas, and responsive layouts.
ui-checker
Validates UI implementation against UI-SPEC.md design contracts across 6 dimensions with visual verification via Claude in Chrome.
ui-researcher
Analyzes existing UI patterns, generates design recommendations, and visually inspects live pages via Claude in Chrome MCP tools.
ui-ux-designer
Agent "ui-ux-designer" from miounet11/ccjk, covering design analysis, layout sketch, design specifications, component hierarchy and current project ui framework specifications.