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/test-generationgit clone --depth 1 https://github.com/Fu-Jie/openwebui-extensionsWrote 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.
[](https://agentmods.dev/instructions/fu-jie/openwebui-extensions/test-generation)<a href="https://agentmods.dev/instructions/fu-jie/openwebui-extensions/test-generation"><img src="https://agentmods.dev/badge/instructions/fu-jie/openwebui-extensions/test-generation.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00851 | $0.00851 |
| Opus 5 | $0.00426 | $0.00426 |
| Sonnet 5 | $0.00170 | $0.00170 |
| Haiku 4.5 | $0.00085 | $0.00085 |
Grade A, and why
Test Generation 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 3d 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.
Test Generation Instructions
You are an expert SDET (Software Development Engineer in Test) writing tests for the openwebui-extensions repository.
Follow these comprehensive guidelines to ensure robust, reliable, and cost-effective testing.
1. Test Structure & Placement
- Unit Tests: Place in the
tests/directory at the root of the repository. Name filestest_<module>.py. - Integration/Debug Scripts: Place in
plugins/debug/<plugin_name>/. Name filesdebug_<feature>.pyorinspect_<feature>.py. - Fixtures: Use
conftest.pyfor shared fixtures (e.g., mock users, mock emitters, mock database sessions).
2. Model Usage & Cost Control (CRITICAL)
When writing tests or debug scripts that actually invoke an LLM:
- Allowed Models: You MUST use low-cost models:
gpt-5-mini(Preferred) orgpt-4.1. - Forbidden: NEVER use expensive models (like
gpt-4-turbo,claude-3-opus) in automated tests unless explicitly requested by the user. - API Keys: Never hardcode API keys. Always read from environment variables (
os.getenv("OPENAI_API_KEY")) or a.envfile.
3. Mocking OpenWebUI Internals
OpenWebUI plugins rely heavily on injected runtime variables. Your tests must mock these accurately:
__user__: Mock as a dictionary. Always test both with a full user object and an empty/None object to ensure fallback logic works.mock_user_en = {"id": "u1", "name": "Alice", "language": "en-US"} mock_user_zh = {"id": "u2", "name": "Bob", "language": "zh-CN"} mock_user_none = None__event_emitter__: Mock as an async callable that records emitted events for assertion.async def mock_emitter(event: dict): emitted_events.append(event)__event_call__: Mock as an async callable. To test Antigravity timeout guards, you must occasionally mock this to sleep longer than the timeout (e.g.,await asyncio.sleep(3.0)) to ensureasyncio.wait_forcatches it.
4. Testing Async Code
- All OpenWebUI plugin entry points (
action,inlet,outlet) are asynchronous. - Use
@pytest.mark.asynciofor all test functions. - Ensure you
awaitall plugin method calls.
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.
- 3d ago First seen · 55 lines · 851 tokens per session scan A dbfed7ff996b
Test Generation is an instructions file published in the GitHub repository Fu-Jie/openwebui-extensions (302 stars, last pushed 1mo ago), licensed MIT. It adds 851 tokens to every session, about $0.0043 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
apm python.instructions.md
Python development guidelines.
llm-ide-rules pytest-tests.instructions.md
Instructions for iloveitaly/llm-ide-rules, covering pytest tests, example test and file structure.
ChainWeaver tests.instructions.md
Instructions for dgenio/ChainWeaver, covering tests, file boundary, framework rules and organization.
python-sdk AGENTS.md
AGENTS.md instructions for ProvableHQ/python-sdk, covering aleo python sdk — agent guide, build & test, architecture conventions (follow these), testing discipline and delegated services (dps + record scanner).
python-ai-guardrails-template CLAUDE.md
Instructions for tortastudios/python-ai-guardrails-template, covering claude code — quality contract, how the quality gate works, fixing failures, critical functions and code style rules.
web-explorer-mcp python-testing-rules.instructions.md
Instructions for l0kifs/web-explorer-mcp, covering rules for an ai agent testing a python project (pytest), basic principles, pytest practices (minimal yet sufficient), quality and coverage and isolation and external effects.