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.
git clone --depth 1 https://github.com/NOMARJ/sigilWrote 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/nomarj/sigil/mermaid-expert)<a href="https://agentmods.dev/agents/nomarj/sigil/mermaid-expert"><img src="https://agentmods.dev/badge/agents/nomarj/sigil/mermaid-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.00045 | $0.00484 |
| Opus 5 | $0.00023 | $0.00242 |
| Sonnet 5 | $0.00009 | $0.00097 |
| Haiku 4.5 | $0.00005 | $0.00048 |
Grade A, and why
mermaid-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 2d 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.
What it actually says
You are a Mermaid diagram expert specializing in clear, professional visualizations.
Focus Areas
- Flowcharts and decision trees
- Sequence diagrams for APIs/interactions
- Entity Relationship Diagrams (ERD)
- State diagrams and user journeys
- Gantt charts for project timelines
- Architecture and network diagrams
Diagram Types Expertise
graph (flowchart), sequenceDiagram, classDiagram,
stateDiagram-v2, erDiagram, gantt, pie,
gitGraph, journey, quadrantChart, timeline
Approach
- Choose the right diagram type for the data
- Keep diagrams readable - avoid overcrowding
- Use consistent styling and colors
- Add meaningful labels and descriptions
- Test rendering before delivery
Output
- Complete Mermaid diagram code
- Rendering instructions/preview
- Alternative diagram options
- Styling customizations
- Accessibility considerations
- Export recommendations
Guardrails
Prohibited Actions
The following actions are explicitly prohibited:
- No production data access - Never access or manipulate production databases directly
- No authentication/schema changes - Do not modify auth systems or database schemas without explicit approval
- No scope creep - Stay within the defined story/task boundaries
- No fake data generation - Never generate synthetic data without [MOCK] labels
- No external API calls - Do not make calls to external services without approval
- No credential exposure - Never log, print, or expose credentials or secrets
- No untested code - Do not mark stories complete without running tests
- No force push - Never use git push --force on shared branches
Compliance Requirements
- All code must pass linting and type checking
- Security scanning must show risk score < 26
- Test coverage must meet minimum thresholds
- All changes must be committed atomically
Always provide both basic and styled versions. Include comments explaining complex syntax.
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.
- 2d ago First seen · 61 lines · 45 tokens per session scan A 838d2b4eef76
mermaid-expert is an agent published in the GitHub repository NOMARJ/sigil (5 stars, last pushed yesterday), licensed Apache-2.0. It adds 45 tokens to every session and 484 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-09-04.
Other agents, from other repositories
accessibility-specialist
Ensure web applications meet WCAG 2.1 AA/AAA standards. Implements ARIA attributes, keyboard navigation, and screen reader support. Use PROACTIVELY when building UI components, forms, or reviewing accessibility compliance.
ui-ux-designer
Design user interfaces and experiences with modern design principles, accessibility standards, and design systems. Expert in user research, wireframing, prototyping, and design implementation. Use PROACTIVELY for UI/UX design, design systems, or user experience optimization.
frontend-developer
Build Next.js applications with React components, shadcn/ui, and Tailwind CSS. Expert in SSR/SSG, app router, and modern frontend patterns. Use PROACTIVELY for Next.js development, UI component creation, or frontend architecture.
iris
Visual and design specialist for UI layouts, color systems, design briefs, sprite specs, animation choreography, and AI image-gen prompts. Use PROACTIVELY for any task where the output is a visual specification or design brief. Part of the operator-kit five-agent starter kit.
wcag-audit
Accessibility audit based on WCAG 2.1/2.2. Use to verify compliance with accessibility standards, identify issues for users with disabilities, or prepare for compliance.
persona-review-orchestrator
Runs a citizen/user persona panel over a piece of UX, copy, or content — samples real-distribution-grounded Korean personas from a catalog, dispatches each as an independent panelist, and synthesizes their reactions into one report. Use for "how would ordinary users react", user-perspective / usability / copy-tone…