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/bex-co/bex/mermaidnpx skills add bex-co/bex --skill mermaidgit clone --depth 1 https://github.com/bex-co/bexWrote 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/bex-co/bex/mermaid)<a href="https://agentmods.dev/skills/bex-co/bex/mermaid"><img src="https://agentmods.dev/badge/skills/bex-co/bex/mermaid.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.00037 | $0.00759 |
| Opus 5 | $0.00018 | $0.00380 |
| Sonnet 5 | $0.00007 | $0.00152 |
| Haiku 4.5 | $0.00004 | $0.00076 |
Grade A, and why
mermaid 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 6d 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 — 31 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Draw a mermaid architecture diagram in markdown for: $ARGUMENTS
Conventions
- Boxes are services/components:
svc[bex-api]. Use[(...)]for datastores. Humans (user, developer, operator) are triangles:user@{ shape: tri, label: "user" }. - A box that is not a long-running service must say so in its label — readers assume boxes are services and ask "where is this running?". Mark scheduled/ephemeral work (
cron["backup pod (spawned nightly, exits when done)"]) and inert config objects (secret["Secret foo (k8s object, created once)"]). Draw humans as triangles:operator@{ shape: tri, label: "operator" }. Never draw a manual procedure as a peer box of running infrastructure: give runbook/recovery flows their own subgraph whose title says it's manual and where it runs (subgraph "disaster recovery — manual runbook, any docker host"), with the human actor inside. - Arrows are dependency direction:
A --> Bmeans A depends on (calls, reads, deploys to) B — never the reverse. - Concise but to the point: only load-bearing services and edges. No styling, no colors, no legend. Label an edge (
A -->|gRPC| B) only when the relationship isn't obvious. Default toflowchart TB; useLRonly if the graph is much wider than deep. Usesubgraphonly for real boundaries (cluster, node, network, trust zone, automated vs. manual) — subgraphs are how the diagram answers "where does this run?". An edge may target a whole subgraph by id (subgraph cluster["app cluster"]…op --> cluster). - If $ARGUMENTS refers to this repo, read the relevant docs/code first (
docs/ADR002-architecture.mdis the map) — don't diagram from guesswork.
Syntax gotchas that break rendering: quote labels containing (, ), [, {, or -->-like text (a["Queue (SQS)"]); never name a node bare end or graph; subgraph titles with spaces need quotes.
Verify (mandatory, before answering)
- Write the diagram body (no
```mermaidfence) to a.mmdfile in the scratchpad (e.g./tmp/diagram.mmdor the current workspace). - Run:
npx -y @mermaid-js/[email protected] -i <file>.mmd -o <file>.svg— exit 0 means the syntax is valid. (First run downloads a headless browser; that's expected.) The version is pinned deliberately (supply-chain: codex-security #17) — bump it consciously, don't revert to floating. - On failure, read the parse error, fix the diagram, and re-verify. Never output a diagram that hasn't passed.
What ships with it
1 file 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.
- 6d ago First seen · 31 lines · 37 tokens per session scan A 0b9840acc9c8
mermaid is a skill published in the GitHub repository bex-co/bex (420 stars, last pushed today), licensed Apache-2.0. It adds 37 tokens to every session and 759 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
gen-test
Generate idiomatic tests for Go packages and handlers in the Meshery project.
lavish
Turn complex or visual agent responses into rich, reviewable HTML artifacts the user can annotate and send feedback on, using the lavish-axi CLI. Use when about to give a plan, comparison, diagram, table, code diff, report, or anything easier to grasp visually than as prose.
bump-go-version
Bumps the Go version to the latest release across go.mod, tools.mod, and Dockerfiles.
project-writing-go-modules-framework-v2
Use when creating or migrating a Go go.d collector to framework V2, touching CollectorV2, metrix.CollectorStore, ChartTemplateYAML/charts.yaml, charttpl/chartengine, V2 host scopes/vnodes, or V2 collector tests. Focuses on concise maintainer-preferred V2 collector patterns.
project-go-collector-design
Early design decisions for Go go.d collectors, made before code. Use when designing a new go.d collector; when adding, renaming, removing, or changing the default of a config option or mode; when adding or changing a Function; when changing what a metric means or which entities become charts or vnodes; when a…
mariadb-operator-pr-review
Perform a structured maintainer-style PR review for the mariadb-operator repository. Gathers PR context, triages the change, and evaluates correctness, safety, pitfalls, backwards compatibility and code quality against the project conventions documented in AGENTS.md. Use whenever the user mentions a mariadb-operator…