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/fu-jie/openwebui-extensions/commit-messagegit clone --depth 1 https://github.com/Fu-Jie/openwebui-extensionsWhat 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.00932 | $0.00932 |
| Opus 5 | $0.00466 | $0.00466 |
| Sonnet 5 | $0.00186 | $0.00186 |
| Haiku 4.5 | $0.00093 | $0.00093 |
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 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.
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
docsor 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, andrefactor. - 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.
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.
- 2d ago First seen · 91 lines · 932 tokens per session scan A 81d92691c942
Commit Message is an instructions file published in the GitHub repository Fu-Jie/openwebui-extensions (301 stars, last pushed 1mo ago), licensed MIT. It adds 932 tokens to every session, about $0.0047 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
cocoindex AGENTS.md
AGENTS.md instructions for cocoindex-io/cocoindex, covering agents.md, build and test commands, building, testing and code formatting and linting.
apm python.instructions.md
Python development guidelines.
framework AGENTS.md
Instructions for ai-driven-dev/framework, covering agents.md, behavior, communication, action and memory management.
packmind packmind-rest-api-endpoint-design.instructions.md
Instructions for PackmindHub/packmind: Conventions for designing REST API endpoints that are predictable, self-documenting, and aligned with distinct business actions. Favors dedicated action endpoints over generic status updates, and rout... .
SwarmAI CLAUDE.md
Instructions for xg-gh-25/SwarmAI, covering claude.md, before you push — the local quality gate, commit identity, dev commands and conventions & invariants.
Meterless AGENTS.md
Instructions for Meterless/Meterless, covering agent instructions for meterless, routing table, isolation rule, repo-wide rules and non-coding agents.