agentmods.dev

gitea-mcp mermaid.instructions.md

Project instructions for creating and checking Mermaid diagrams, which describe diagrams as text and can be previewed in Visual Studio Code.

In plain words
What is it for?
Use them when creating, editing, validating, or previewing diagrams in Visual Studio Code.
Why use it?
They define a repeatable process for writing Mermaid files, checking their syntax, and previewing the result.

Instructions file for GitHub Copilot

0 24d ago A scan 970 tokens copy · 100% MIT
View the source file datamathcode/gitea-mcp
Install

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.

agentmods
npx agentmods add instructions/datamathcode/gitea-mcp/mermaid
Clone the repo
git clone --depth 1 https://github.com/datamathcode/gitea-mcp

Made for: GitHub Copilot.

Per session 970 This file is loaded in full into every session.
When invoked 970 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00970 $0.00970
Opus 5 $0.00485 $0.00485
Sonnet 5 $0.00194 $0.00194
Haiku 4.5 $0.00097 $0.00097

Measured yesterday against content hash 6a91984bb661, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

gitea-mcp mermaid.instructions.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 yesterday.

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.

Origin

This is a copy

100% identical to coding mermaid.instructions.md — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.github/instructions/mermaid.instructions.md · 86 lines

How it starts

The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Mermaid AI Skills

When the user asks to create, edit, or visualize any diagram, use the Mermaid VS Code extension tools and commands described below.

Workflow

  1. Determine the diagram type and generate Mermaid syntax.
  2. Write the diagram to a .mmd file in the project.
  3. Validate syntax: correct first-line keyword, arrow types, balanced brackets.
  4. Preview via the Mermaid extension — open the .mmd file (auto-preview) or run MermaidChart: Preview Diagram (mermaidChart.preview).

LM Tools — call these for every diagram interaction

  • mermaid-diagram-validator — validate Mermaid syntax before presenting any diagram
  • mermaid-diagram-preview — render a live preview inside VS Code after generating
  • get-syntax-docs-mermaid — fetch correct syntax docs for any diagram type

VS Code Commands

Invoke via Command Palette or the VS Code command API (GitHub Copilot in VS Code only). Do not invent command IDs. Prefer writing/editing .mmd files when a command is not needed.

Diagram editing & preview

  • Preview (mermaidChart.preview) — preview the active Mermaid editor (.mmd / .mermaid must be open).
  • Create Diagram (mermaidChart.createMermaidFile) — creates a demo flowchart and opens preview side by side.
  • Repair Diagram (mermaidChart.repairDiagram) — Mermaid AI repair for the active diagram; uses Mermaid AI credits — tell the user before running.
  • Improve Diagram (mermaidChart.improveDiagram) — uses Copilot / LM API; suggests layout + styling variants for the active diagram.

Generate diagrams (GitHub Copilot required)

  • Generate Diagram from Code (mermaidChart.generateDiagramFromCode)
  • Generate Cloud Diagram (mermaidChart.generateCloudDiagram)
  • Generate ER Diagram (mermaidChart.generateERDiagram)
  • Generate Docker Diagram (mermaidChart.generateDockerDiagram)
  • Open AI Chat (mermaidChart.openCopilotChat)

Mermaid Chart cloud

  • Login (mermaidChart.login) / Logout (mermaidChart.logout)
  • Connect Diagram (mermaidChart.connectDiagramToMermaidChart) — link a local diagram to Mermaid Chart.
  • Sync Diagram (mermaidChart.syncDiagramWithMermaid) — only for diagrams already connected (frontmatter has id:). Example: 
    ---
id: cbd9e9ba-a2cb-47c5-a98e-8c28a753428d
---

Read the full file on GitHub · 86 lines

Changes

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.

  1. yesterday First seen · 86 lines · 970 tokens per session scan A 6a91984bb661

Subscribe to this mod's changes

gitea-mcp mermaid.instructions.md is an instructions file published in the GitHub repository datamathcode/gitea-mcp (0 stars, last pushed 24d ago), licensed MIT. It adds 970 tokens to every session, about $0.0049 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to coding mermaid.instructions.md, differing in 0 lines, and is treated as a copy.

Productivity
Related

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).

microsoft/vscode · 6,785 tokens

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.

github/spec-kit · 7,104 tokens

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.

openai/codex · 5,182 tokens

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.

langchain-ai/langchain · 4,345 tokens

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).

microsoft/vscode · 5,001 tokens

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.

vercel/next.js · 7,296 tokens