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/code-reviewgit 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.00899 | $0.00899 |
| Opus 5 | $0.00449 | $0.00449 |
| Sonnet 5 | $0.00180 | $0.00180 |
| Haiku 4.5 | $0.00090 | $0.00090 |
Grade A, and why
Plugin Code Review 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review Instructions — OpenWebUI Plugins
You are an expert Senior Software Engineer reviewing OpenWebUI plugins for the openwebui-extensions repository.
When reviewing plugin code, you MUST verify each point below to ensure the code meets the strict repository standards.
1. Single-file i18n Pattern (CRITICAL)
- One File Rule: One
.pyfile per plugin. No_cn.pyor language-split files. - Translations: All user-visible strings (status, notification, UI text) MUST go through a
TRANSLATIONSdictionary and aFALLBACK_MAP. - Safety:
format(**kwargs)calls on translated strings MUST be wrapped intry/except KeyErrorto prevent crashes if a translation is missing a placeholder.
2. Context Helpers (CRITICAL)
- User Context: MUST use
_get_user_context(__user__)instead of direct__user__["name"]access.__user__can be a list, dict, or None. - Chat Context: MUST use
_get_chat_context(body, __metadata__)instead of ad-hocbody.get("chat_id")calls.
3. Event & Logging
- No Print: No bare
print()in production code. Uselogging.getLogger(__name__). - Emitter Safety: Every
await emitter(...)call MUST be guarded byif emitter:(or equivalent). - Status Lifecycle:
_emit_status(done=False)at task start._emit_status(done=True)on completion._emit_notification("error")on failure.
4. Antigravity Safety (CRITICAL)
- Timeout Guards: All
__event_call__JS executions MUST be wrapped withasyncio.wait_for(..., timeout=2.0). Failure to do this can hang the entire backend. - JS Fallbacks: JS code executed via
__event_call__MUST have an internaltry { ... } catch (e) { return fallback; }block. - Path Sandboxing: File path operations MUST be validated against the workspace root (no directory traversal vulnerabilities).
- Upload Fallbacks: Upload paths MUST have a dual-channel fallback (API → local/DB).
5. Filter Singleton Safety
- No Mutable State: Filter plugins are singletons. There MUST be NO request-scoped mutable state stored on
self(e.g.,self.current_user = ...). - Statelessness: Per-request values MUST be computed from
bodyand context helpers on each call.
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 · 55 lines · 899 tokens per session scan A 1b01c9e2ab07
Plugin Code Review is an instructions file published in the GitHub repository Fu-Jie/openwebui-extensions (302 stars, last pushed 1mo ago), licensed MIT. It adds 899 tokens to every session, about $0.0045 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.
openscreen AGENTS.md
Instructions for getopenscreen/openscreen, covering agents.md, setup commands, development principles, project layout and code style.
apm python.instructions.md
Python development guidelines.
GameDesignOS AGENTS.md
Instructions for DY-2026/GameDesignOS, covering gamedesignos agent 入口, 默认接法, agent 执行规则, 什么时候用整个项目 and 每个 skill 单独怎么用.
framework AGENTS.md
Instructions for ai-driven-dev/framework, covering agents.md, behavior, communication, action and memory management.
document CLAUDE.md
Claude Code instructions for ranuts/document, covering claude.md — document 项目指南, 项目概述, 提交流程（2026-08-16 起：pr 制，main 受保护）, 开发命令 and 目录结构.