Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
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.
[](https://agentmods.dev/skills/fu-jie/openwebui-extensions/test-copilot-pipe)<a href="https://agentmods.dev/skills/fu-jie/openwebui-extensions/test-copilot-pipe"><img src="https://agentmods.dev/badge/skills/fu-jie/openwebui-extensions/test-copilot-pipe.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.1 | $0.00026 | $0.00874 |
| Opus 5 | $0.00013 | $0.00437 |
| Sonnet 5 | $0.00005 | $0.00175 |
| Haiku 4.5 | $0.00003 | $0.00087 |
Grade A, and why
test-copilot-pipe 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 7d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🤖 Skill: Test Copilot Pipe
This is a universal testing framework for publishing the latest github_copilot_sdk.py (Pipe) code to a local OpenWebUI instance and verifying it via an automated agent (browser_subagent).
🎯 Core Principles
- Fixed Infrastructure: The deployment script and the test entry URL are always static.
- Dynamic Test Planning: Specific test prompts and expectations (acceptance criteria) must be dynamically planned by you based on the code changes or specific user requests before execution.
🛠️ Static Environment Info
| Attribute | Fixed Value |
|---|---|
| Deployment Script | /Users/fujie/app/python/oui/openwebui-extensions/scripts/deploy_pipe.py |
| Python Path | /opt/homebrew/Caskroom/miniconda/base/envs/ai/bin/python3 |
| Test URL | http://localhost:3003/?model=github_copilot_official_sdk_pipe.github_copilot_sdk-gpt-4.1 |
📋 Standard Workflow
Step 1: Analyze Changes & Plan Test (Plan)
Before triggering the test, you must define the purpose of this test turn. Example: Modified tool calling logic -> Test prompt should trigger a specific tool; observe if the tool executes and returns the correct result.
Step 2: Deploy Latest Code (Deploy)
Use the run_command tool to execute the fixed update task:
/opt/homebrew/Caskroom/miniconda/base/envs/ai/bin/python3 /Users/fujie/app/python/oui/openwebui-extensions/scripts/deploy_pipe.py
Mechanism:
deploy_pipe.pyautomatically loads the API Key fromscripts/.envin the same directory. Verification: Look for✅ Successfully updated... version X.X.Xor✅ Successfully created.... If a 401 error occurs, remind the user to generate a new API Key in OpenWebUI and update.env.
Step 3: Verify via Browser Subagent (Verify)
Use the browser_subagent tool. You must fill in the [Dynamic Content] slots based on Step 1:
Task:
1. Access The Fixed URL: http://localhost:3003/?model=github_copilot_official_sdk_pipe.github_copilot_sdk-gpt-4.1
2. RELIABILITY WAIT: Wait until the page fully loads. Wait until the chat input text area (`#chat-input`) is present in the DOM.
3. ACTION - FAST INPUT: Use the `execute_browser_javascript` tool to instantly inject the query and submit it. Use exactly this script format to ensure stability:
`const input = document.getElementById('chat-input'); input.value = "[YOUR_DYNAMIC_TEST_PROMPT]"; input.dispatchEvent(new Event('input', { bubbles: true })); const e = new KeyboardEvent('keydown', { key: 'Enter', code: 'Enter', keyCode: 13, which: 13, bubbles: true }); input.dispatchEvent(e);`
4. WAITING: Wait patiently for the streaming response to stop completely. You should wait for the Stop button to disappear, or wait for the system to settle (approximately 10-15 seconds depending on the query).
5. CHECK THE OUTCOME: [List the phenomena you expect to see, e.g., status bar shows specific text, tool card appears, result contains specific keywords, etc.]
6. CAPTURE: Take a screenshot of the settled state to prove the outcome.
7. REPORT: Report the EXACT outcome matching the criteria from step 5.
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.
- 7d ago First seen · 65 lines · 26 tokens per session scan A 853ec4fa671a
test-copilot-pipe is a skill published in the GitHub repository Fu-Jie/openwebui-extensions (304 stars, last pushed 2d ago), licensed MIT. It adds 26 tokens to every session and 874 once invoked, about $0.0001 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 skills, from other repositories
validate
Validate Semantica pipelines, extraction quality, graph schemas, and ontology consistency. Returns structured error/warning checklists. Uses PipelineValidator, PipelineBuilder.validatepipeline(), GraphValidator, and OntologyValidator. Sub-commands: pipeline, step, dependencies, extraction, graph, ontology, performance.
gsd-eval-review
Audit an executed AI phase's evaluation coverage and produce an EVAL-REVIEW.md remediation plan.
gsd-validate-phase
Retroactively audit and fill Nyquist validation gaps for a completed phase.
gsd-audit-uat
Cross-phase audit of all outstanding UAT and verification items.
handoff
Prepare a clean cross-session handoff so the next agent can pick up where you left off. Writes a focused continue.md in the active slice dir and ensures STATE.md + summary artifacts are current. Use when asked to "hand off", "prepare handoff", "pause work", "bookmark this", "I'll come back to this later", before…
tdd
Test-driven development with red-green-refactor loops around vertical slices (tracer bullets), not horizontal layers. Use when asked to "use TDD", "write test-first", "red-green-refactor", "build this with tests", or when a feature has a clear observable contract. The discipline complement to the test/add-tests skills…