openwebui-extensions: Instructions file for GitHub Copilot

.github/instructions/commit-message.instructions.md

Commit Message is an instructions file for GitHub Copilot from Fu-Jie/openwebui-extensions. It costs 932 tokens per session, scanned A, original, MIT.

A set of rules for writing Git commit messages using the Conventional Commits format, such as feat for a feature or fix for a bug. It defines the allowed types, scopes, language, and message structure.

In plain words
What is it for?
Use it when naming commits for plugin features, bug fixes, documentation, tests, refactoring, or build-related changes.
Why use it?
It removes uncertainty about how commits should be titled and organized. Consistent messages make project history easier to read and automate.

Instructions file for GitHub Copilot

Written for GitHub Copilot: a Copilot instructions file.

This is Fu-Jie/openwebui-extensions's own configuration. It tells GitHub Copilot how to work on openwebui-extensions itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything openwebui-extensions configures →

Reuse

Borrowing it

Nothing to install: this file belongs to Fu-Jie/openwebui-extensions. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/Fu-Jie/openwebui-extensions/main/.github/instructions/commit-message.instructions.md
Clone the repo
git clone --depth 1 https://github.com/Fu-Jie/openwebui-extensions

Made for: GitHub Copilot.

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

agentmods badge for Commit Message

README.md
[![agentmods](https://agentmods.dev/badge/instructions/fu-jie/openwebui-extensions/commit-message/github.svg)](https://agentmods.dev/instructions/fu-jie/openwebui-extensions/commit-message)
Your own site
<a href="https://agentmods.dev/instructions/fu-jie/openwebui-extensions/commit-message"><img src="https://agentmods.dev/badge/instructions/fu-jie/openwebui-extensions/commit-message/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.

agentmods 80×15 button for Commit Message

Your own site · 80×15
<a href="https://agentmods.dev/instructions/fu-jie/openwebui-extensions/commit-message"><img src="https://agentmods.dev/badge/instructions/fu-jie/openwebui-extensions/commit-message.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 932 This file is loaded in full into every session.
When invoked 932 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00932 $0.00932
Opus 5.5 $0.00373 $0.00373
Sonnet 5.5 $0.00186 $0.00186
Haiku 4.5 $0.00093 $0.00093

Measured 2mo ago against content hash 81d92691c942, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

Commit Message 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 2mo 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/instructions/commit-message.instructions.md · 91 lines

How it starts

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

Commit Message Instructions

You are an expert developer generating commit messages for the openwebui-extensions repository. Always adhere to the following strict guidelines based on the Conventional Commits specification.

1. General Rules

  • Language: English ONLY. Never use Chinese or other languages in the commit title or body.
  • Structure:
    <type>(<scope>): <subject>
    <BLANK LINE>
    <body>
    <BLANK LINE>
    <footer>
    

2. Type (<type>)

Must be one of the following:

  • feat: A new feature or a new plugin.
  • fix: A bug fix.
  • docs: Documentation only changes (e.g., README, MkDocs).
  • 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.
  • chore: Changes to the build process, CI/CD, or auxiliary tools/scripts.
  • style: Changes that do not affect the meaning of the code (white-space, formatting, etc.).

3. Scope (<scope>)

The scope should indicate the affected component or plugin.

  • For Plugins: Use the plugin's folder name or category (e.g., actions, filters, pipes, export-to-docx, github-copilot-sdk).
  • For Docs: Use docs or the specific doc section (e.g., guide, readme).
  • For Infra: Use ci, scripts, deps.
  • Note: Omit the scope if the change is global or spans too many components.

4. Subject Line (<subject>)

  • Length: Keep it under 50-72 characters.
  • Mood: Use the imperative, present tense: "change" not "changed" nor "changes" (e.g., "add feature" instead of "added feature").
  • Formatting: Do not capitalize the first letter. Do not place a period . at the end.
  • Clarity: State exactly what changed. Avoid vague terms like "update code" or "fix bug".

5. Body (<body>)

  • When to use: Highly recommended for feat, fix, and refactor.
  • Content: Explain what and why (motivation), not just how (the code diff shows the how).
  • Format: Use a bulleted list (1-3 points) for readability.
  • Repo Specifics: If the commit involves a plugin version bump, explicitly mention that the READMEs and docs were synced.

Read the full file on GitHub · 91 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. 2mo ago First seen · 91 lines · 932 tokens per session scan A 81d92691c942

Subscribe to this mod's changes

Commit Message is an instructions file published in the GitHub repository Fu-Jie/openwebui-extensions (333 stars, last pushed 27d ago), licensed MIT. It adds 932 tokens to every session, about $0.0037 per session on Opus 5.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.

Related

Commit Message compared with instructions from other repositories

Commit Message next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
Commit MessageFu-Jie/openwebui-extensionsInstructions file33327d agoMITA932GitHub Copilot
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143ktodayMITA7,461Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchainInstructions file149ktodayMITA4,680Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA5,516GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA3,093GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file274k2d agoMITA4,313Codex, OpenCode