commit-convention-mcp copilot-instructions.md

Project instructions for an MCP server that provides Git commit-convention tools and resources. Git is a version-control system, and commit conventions are shared rules for writing change descriptions.

In plain words
What is it for?
Use them when generating commit messages for this project or when changing its HTML, CSS, JavaScript, TypeScript, React, or Vue code.
Why use it?
They define which prompt and repository changes to use when generating a commit message. They also require a frontend guideline file when creating or modifying frontend code.

Instructions file for GitHub Copilot

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/myutex/commit-convention-mcp/copilot-instructions
Clone the repo
git clone --depth 1 https://github.com/myutex/commit-convention-mcp

Made for: GitHub Copilot.

Per session 492 This file is loaded in full into every session.
When invoked 492 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found 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.00492 $0.00492
Opus 5 $0.00246 $0.00246
Sonnet 5 $0.00098 $0.00098
Haiku 4.5 $0.00049 $0.00049

Measured 2d ago against content hash 31e384c3771e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

commit-convention-mcp copilot-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 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.

.github/copilot-instructions.md · 12 lines

What it actually says

다음 MCP 서버 사용 규칙 및 코드 생성 지침을 준수하십시오:

  1. 최신 정보/문서: 라이브러리에 대한 최신 정보나 문서가 필요할 경우, context7 MCP 서버 (github.com/upstash/context7-mcp)를 우선적으로 사용하십시오. (resolve-library-id를 먼저 사용하여 정확한 ID를 확인해야 할 수 있습니다.)

  2. Git 커밋 메시지: 커밋 메시지 생성 요청 시, 반드시 commit-convention-mcp MCP 서버를 사용하고 다음 작업 순서를 따르십시오. 이는 Git 관련 명령의 원활한 실행을 보장합니다: a. get_commit_message_prompt를 사용하여 해당 서버의 프롬프트 리소스(예: prompt://git/commit-message/standard/v1)를 가져옵니다. 이 프롬프트는 커밋 메시지 생성의 기준이 됩니다. b. 가져온 프롬프트를 확인하여, 커밋 메시지 생성을 위해 특정 git 명령어(예: git diff, git diff --staged) 실행 결과가 명시적으로 요구되는지 확인합니다. c. 프롬프트에서 특정 git 명령어 실행 결과가 필요하다고 명시된 경우, 프롬프트에 지정된 정확한 명령어를 실행하여 변경사항을 가져옵니다. (사용자에게 어떤 명령어를 사용할지 묻지 않습니다.) d. 가져온 프롬프트 템플릿과 (프롬프트 요구 시) 실행된 git 명령어 결과를 사용하여 최종 커밋 메시지를 생성합니다. 예를 들어, 프롬프트 내의 {{diff}}와 같은 플레이스홀더를 가져온 git diff 결과로 대체할 수 있습니다.

  3. 프론트엔드 코드 생성: 프론트엔드 코드(HTML, CSS, JavaScript, TypeScript, React, Vue 등) 생성 또는 수정 요청 시, 현재 작업 디렉토리에 있는 docs/frontend-guideline.md 파일(토스 프론트엔드 지침서 내용)을 반드시 참고하여 코드 스타일과 규칙을 준수하십시오.

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. 2d ago First seen · 12 lines · 492 tokens per session scan A 31e384c3771e

Subscribe to this mod's changes

commit-convention-mcp copilot-instructions.md is an instructions file published in the GitHub repository myutex/commit-convention-mcp (2 stars, last pushed 1y ago), licensed MIT. It adds 492 tokens to every session, about $0.0025 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.

Related

Other instructions, from other repositories

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

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

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