Borrowing it
Nothing to install: this file belongs to yohasacura/drawio-mcp. 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/yohasacura/drawio-mcp/main/.github/instructions/git-style.instructions.mdgit clone --depth 1 https://github.com/yohasacura/drawio-mcpWrote 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/yohasacura/drawio-mcp/git-style)<a href="https://agentmods.dev/instructions/yohasacura/drawio-mcp/git-style"><img src="https://agentmods.dev/badge/instructions/yohasacura/drawio-mcp/git-style/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/yohasacura/drawio-mcp/git-style"><img src="https://agentmods.dev/badge/instructions/yohasacura/drawio-mcp/git-style.svg" alt="Reviewed on agentmods" width="80" 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.02728 | $0.02728 |
| Opus 5 | $0.01364 | $0.01364 |
| Sonnet 5 | $0.00546 | $0.00546 |
| Haiku 4.5 | $0.00273 | $0.00273 |
Grade A, and why
drawio-mcp git-style.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 9d 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 — 476 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Style Guide
Overview
This guide establishes standards for Git usage to maintain a clean, comprehensible, and stable version control history. Following these practices ensures that the repository remains navigable, collaborative changes are clear, and the project history tells a coherent story.
Commit Messages
Structure
Every commit message should follow this format:
<type>(<scope>): <subject>
<body>
<footer>
Type
Must be one of the following:
- feat: A new feature for the user
- fix: A bug fix
- docs: Documentation only changes
- style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
- refactor: A code change that neither fixes a bug nor adds a feature
- perf: A code change that improves performance
- test: Adding missing tests or correcting existing tests
- build: Changes that affect the build system or external dependencies
- ci: Changes to CI configuration files and scripts
- chore: Other changes that don't modify src or test files
- revert: Reverts a previous commit
Scope
The scope should specify the place of the commit change. For this project:
- backend: Changes to the backend API
- frontend: Changes to the frontend application
- api: REST API endpoints or services
- ui: User interface components
- auth: Authentication/authorization
- db: Database schema or migrations
- config: Configuration files
- deps: Dependencies updates
Subject
The subject contains a succinct description of the change:
- Use the imperative, present tense: "change" not "changed" nor "changes"
- Don't capitalize the first letter
- No period (.) at the end
- Maximum 50 characters
- Be specific and descriptive
Body (Optional but Recommended)
The body should include:
- Motivation for the change
- Contrast with previous behavior
- Wrap at 72 characters
- Use bullet points for multiple items
Footer (Optional)
The footer should contain:
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.
- 9d ago First seen · 476 lines · 2,728 tokens per session scan A ed83082fb364
drawio-mcp git-style.instructions.md is an instructions file published in the GitHub repository yohasacura/drawio-mcp (5 stars, last pushed 7mo ago), licensed MIT. It adds 2,728 tokens to every session, about $0.0136 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-31.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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.
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).
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).
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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.