Borrowing it
Nothing to install: this file belongs to Fu-Jie/openwebui-extensions. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Fu-Jie/openwebui-extensions/main/.gemini/skills/openwebui-community-publisher/SKILL.mdgit 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/skills/fu-jie/openwebui-extensions/openwebui-community-publisher)<a href="https://agentmods.dev/skills/fu-jie/openwebui-extensions/openwebui-community-publisher"><img src="https://agentmods.dev/badge/skills/fu-jie/openwebui-extensions/openwebui-community-publisher/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.
<a href="https://agentmods.dev/skills/fu-jie/openwebui-extensions/openwebui-community-publisher"><img src="https://agentmods.dev/badge/skills/fu-jie/openwebui-extensions/openwebui-community-publisher.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00018 | $0.00580 |
| Opus 5 | $0.00009 | $0.00290 |
| Sonnet 5 | $0.00004 | $0.00116 |
| Haiku 4.5 | $0.00002 | $0.00058 |
Grade A, and why
openwebui-community-publisher 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 11d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenWebUI Community Publisher
Overview
This skill automates the process of creating new plugin release notes and announcements directly on the OpenWebUI Community (openwebui.com).
Note: This skill is exclusively for new post creation. Do NOT use this for updating existing posts, as updates are managed separately via dedicated scripts.
Prerequisites
- User must be logged into openwebui.com in the browser session.
- The content must be prepared in Markdown format (typically following the structure of the plugin's changelog or a dedicated release
.mdfile).
Execution Workflow
1. Verification
- Use
browser_subagentto navigate tohttps://openwebui.com. - Verify the logged-in user status (look for profile icons or "@Fu-Jie").
2. Post Creation
- Navigate to
https://openwebui.com/post. - Post Type Selection:
- Choose the appropriate tab based on content:
- Text: General announcements and documentation.
- Tool: Standalone tool plugins.
- Function: Pipes, Filters, or Actions.
- Prompt: Chat prompt templates.
- Model: GGUF/Ollama model files.
- Unless otherwise specified, default to Text for general release introductions.
- Choose the appropriate tab based on content:
- Community Selection:
- For general OpenWebUI related posts, select o/openwebui.
- For specialized topics, select the relevant community (e.g., o/ollama for models).
- Metadata Mapping:
- Title: Use the main header from the source file.
- Content/Description: Paste the Markdown body.
- Source Code (for Function/Pipe): If publishing a
Function, retrieve the corresponding.pyfile content and paste it into the code area.
- Tags: Leave empty by default unless relevant keywords are explicitly provided.
- Media: Optional, only attach if provided.
- Settings: Ensure "Adult content" is unchecked.
3. Submission & Validation
- Click the "Create" (创建) button.
- Wait for redirection to the final post URL.
- CRITICAL: Use
capture_browser_screenshotto verify the rendering. - Return the final URL to the user.
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.
- 11d ago First seen · 60 lines · 18 tokens per session scan A e57e6fc1df72
openwebui-community-publisher is a skill published in the GitHub repository Fu-Jie/openwebui-extensions (307 stars, last pushed 6d ago), licensed MIT. It adds 18 tokens to every session and 580 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
gsd-graphify
Build, query, and inspect the project knowledge graph in .planning/graphs/.
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…
user-general-facts
Capture and organize general facts about the user by topic.
02-project-memory
Build the project's memory of its architecture, conventions, and decisions, and wire it into your AI tools. Use when the user wants to set up or refresh project memory, or rewire it into a tool. Not for editing one existing memory file.
project-context
Use PowerContext project memory and handoff tools through MCP when continuing prior work, recalling decisions, maintaining durable memory, or transferring work across tasks, sessions, or agents.
daily-logs
Track daily activity logs and summaries for the user. TRIGGER BY: read/edit user memory.