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 instructions/mozi-app/mermaid/agents-mdgit clone --depth 1 https://github.com/mozi-app/mermAIdWrote 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/instructions/mozi-app/mermaid/agents-md)<a href="https://agentmods.dev/instructions/mozi-app/mermaid/agents-md"><img src="https://agentmods.dev/badge/instructions/mozi-app/mermaid/agents-md.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.00365 | $0.00365 |
| Opus 5 | $0.00182 | $0.00182 |
| Sonnet 5 | $0.00073 | $0.00073 |
| Haiku 4.5 | $0.00036 | $0.00036 |
Grade A, and why
mermAId AGENTS.md 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.
What it actually says
AGENTS.md
Go backend + JS frontend Mermaid diagram editor with live preview.
Testing
Go tests
- Framework: goconvey (
github.com/smartystreets/goconvey) - Run:
go test -v -race -count=1 -timeout 30s ./... - Always run with
-race - Files:
diagram_test.go,main_test.go,mcp_test.go - Use
stateDirOverride(inmain.go) to redirect state files tot.TempDir()in tests that touch the filesystem
JS tests
- Framework: vitest
- Run:
npm test - Test file:
frontend/parser.test.js
Test rules
- Never use
time.Sleepin tests — use channel +select+ timeout for async assertions - The
frontend/parser.jsis intentionally separated fromeditor.jsso it can be tested without pulling in mermaid/CodeMirror dependencies
Build
make build— full build (npm install + esbuild bundle + go build)make dev— development mode with watchmake test— run Go tests onlynpm test— run JS tests only
Plans
Implementation plans under .agents/plans/ are session scratch and are
gitignored. Do not commit them. Agents write a plan once and never update it,
so the plan goes stale fast. A stale plan misleads the next agent, because the
agent reads it as current. Decisions that outlive the work go in the PR
description, the commit message, or a comment at the line where the constraint
applies. Rules that bind future work go in AGENTS.md.
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 · 37 lines · 365 tokens per session scan A d5454e2999a0
mermAId AGENTS.md is an instructions file published in the GitHub repository mozi-app/mermAId (12 stars, last pushed 23d ago), licensed Apache-2.0. It adds 365 tokens to every session, about $0.0018 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.