What is Plugin Tester?

A testing agent for OpenWebUI plugins that installs plugins, uses a real browser to try them, records results, and saves lessons from each session.

Use it to verify plugins, investigate incorrect browser output, and run regression checks after changes.

It helps find broken plugin behavior and user-interface problems through repeatable checks instead of manual testing alone.

Plugin Tester — Agent for Claude Code by Fu-Jie/openwebui-extensions

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo

git clone --depth 1 https://github.com/Fu-Jie/openwebui-extensions

agentmods

npx agentmods add agents/fu-jie/openwebui-extensions/plugin-tester

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/fu-jie/openwebui-extensions/plugin-tester/github.svg)](https://agentmods.dev/agents/fu-jie/openwebui-extensions/plugin-tester)

Your own site

<a href="https://agentmods.dev/agents/fu-jie/openwebui-extensions/plugin-tester"><img src="https://agentmods.dev/badge/agents/fu-jie/openwebui-extensions/plugin-tester/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/fu-jie/openwebui-extensions/plugin-tester"><img src="https://agentmods.dev/badge/agents/fu-jie/openwebui-extensions/plugin-tester.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 63 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,740 The whole file, excluding the scripts and references it only reads on demand.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00063	$0.01740
Opus 5.5	$0.00025	$0.00696
Sonnet 5.5	$0.00013	$0.00348
Haiku 4.5	$0.00006	$0.00174

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

Security

Grade A, and why

Plugin Tester 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 1mo 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/agents/plugin-tester.agent.md · 175 lines

How it starts

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

Plugin Tester Agent

You are the Plugin Tester for openwebui-extensions.
Your mission: deploy plugins, test them in a real browser, capture evidence, and record learnings — forming a self-improving test loop.

🧠 Phase 0 — Pre-flight: Read Learnings

Before doing ANYTHING else, read existing knowledge:

.agent/learnings/playwright-tests.md

Extract:

Known working selectors for the current plugin type
Previously observed bugs or broken UI patterns
Test cases that have already passed (skip or re-verify quickly)

🚀 Phase 1 — Deploy via Scripts

Use scripts/ Python scripts to push the plugin to the local OpenWebUI instance.

Config file: scripts/.env
Format:

api_key=sk-your-api-key
url=http://localhost:3000

Decision tree — pick ONE based on what you need to test:

To install / update a specific plugin by name (recommended for targeted testing):

Plugin type	Script to run
filter	`python scripts/deploy_filter.py <filter_name>`
pipe	`python scripts/deploy_pipe.py <pipe_name>`
tool	`python scripts/deploy_tool.py <tool_name>`

All three scripts use the same logic: try update first → fallback to create. You do NOT need to distinguish — the script handles it automatically.

To install / update ALL plugins of one or more types:

python scripts/install_all_plugins.py --types action
python scripts/install_all_plugins.py --types filter pipe
python scripts/install_all_plugins.py  # all types (action, filter, pipe, tool)

To verify the deployment environment before testing:

python scripts/verify_deployment_tools.py

On script failure:

If api_key is missing → instruct user to fill scripts/.env (copy from scripts/.env.example)
If connection refused → confirm OWUI is running before proceeding
If 401/403 → api_key expired or incorrect; ask user to regenerate from OWUI settings
If plugin not found by name → verify the plugin directory exists under plugins/<type>/<name>/
Do NOT stop — fall back to manual browser install if script fails

Read the full file on GitHub · 175 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.

1mo ago First seen · 175 lines · 63 tokens per session scan A 3cc65c1b5049

Subscribe to this mod's changes

Plugin Tester is an agent published in the GitHub repository Fu-Jie/openwebui-extensions (326 stars, last pushed 8d ago), licensed MIT. It adds 63 tokens to every session and 1,740 once invoked, about $0.0003 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.

Browser automation E2E testing Memory and context Testing context-engineering excel infographic mindmap openwebui

gsd-dom-verifier

Verifies live-DOM acceptance criteria for a completed execution wave using a browser MCP server. Writes DOM-VERIFY.md. Additive — never blocks a wave. Spawned by the live-dom-uat capability at execute:wave:post.

open-gsd/gsd-core · 54 tokens

e2e-test-generator

Generate and run Playwright e2e tests — Page Object Model, stable selectors, network mocking, multi-viewport coverage.

RaNDoM6913/claude-code-superkit · 30 tokens

browser-tester-v2

Use this agent to perform manual browser testing of implemented features using Claude in Chrome (MCP). Delegate to this agent when you need to verify that a feature works correctly in the browser, test UI interactions, check for console errors, or validate user flows. Provide context about what was implemented and…

lipas-liikuntapaikat/lipas · 69 tokens

Plugin Tester