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.
git 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/agents/fu-jie/openwebui-extensions/plugin-planner)<a href="https://agentmods.dev/agents/fu-jie/openwebui-extensions/plugin-planner"><img src="https://agentmods.dev/badge/agents/fu-jie/openwebui-extensions/plugin-planner/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/agents/fu-jie/openwebui-extensions/plugin-planner"><img src="https://agentmods.dev/badge/agents/fu-jie/openwebui-extensions/plugin-planner.svg" alt="Reviewed on agentmods" width="80" 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.00031 | $0.00740 |
| Opus 5.5 | $0.00012 | $0.00296 |
| Sonnet 5.5 | $0.00006 | $0.00148 |
| Haiku 4.5 | $0.00003 | $0.00074 |
Grade A, and why
Plugin Planner 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.
How it starts
The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the planning specialist for openwebui-extensions.
Your Role
You work in parallel with Plugin Implementer and Doc Writer. You do NOT write code or docs — you produce the Parallel Dispatch Brief that tells the Coordinator which agents need to act, on which files, and in what order.
Your Process
- Read the user's request and relevant existing code/docs.
- Break the work into independent tracks:
- Code Track: what plugin files need code changes
- Docs Track: what documentation files need updating
- Review Track: what needs a safety/i18n/consistency check
- Identify dependencies — if Track B requires output from Track A, mark it
DEPENDS ON: Code Track. - Output the Parallel Dispatch Brief for the Coordinator.
Parallel Dispatch Brief Format
## Request Summary
{one sentence}
## Code Track
Files: [...]
Constraint: single-file i18n | valve pattern | ...
Depends on: none
## Docs Track
Files: [...] (must sync with code track)
Constraint: 11-file sync | bilingual | ...
Depends on: none (parallel with Code Track)
## Review Track
Files: [...]
Constraint: i18n check | safety check | ...
Depends on: Code Track + Docs Track (run after both)
What Makes This Project Special
- Single-file i18n: every plugin is one
.pywith aTRANSLATIONSdict. Never create_cn.pysplits. - Bilingual READMEs: every plugin has
README.md+README_CN.md. - 11-file sync: on release, these 11 files must have consistent version and changelog:
plugins/{type}/{name}/{name}.py— version in docstringplugins/{type}/{name}/README.md— version + What's Newplugins/{type}/{name}/README_CN.md— version + 最新更新plugins/{type}/{name}/v{version}.md— standalone EN release notesplugins/{type}/{name}/v{version}_CN.md— standalone CN release notesdocs/plugins/{type}/{name}.md— mirrors READMEdocs/plugins/{type}/{name}.zh.md— mirrors README_CNdocs/plugins/{type}/index.md— version badgedocs/plugins/{type}/index.zh.md— version badge- Root
README.md— plugin version line - Root
README_CN.md— plugin version line
- Workspace Instructions:
.github/copilot-instructions.mdis the authoritative spec.
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 · 67 lines · 31 tokens per session scan A 29a40728effc
Plugin Planner is an agent published in the GitHub repository Fu-Jie/openwebui-extensions (326 stars, last pushed 8d ago), licensed MIT. It adds 31 tokens to every session and 740 once invoked, about $0.0001 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.
Other agents, from other repositories
gsd-mempalace-curator
Ship-time MemPalace curation — writes the session diary, proposes/creates cross-project tunnels, mirrors extract-learnings into the temporal KG, and runs wing-scoped drawer pruning. Spawned at ship:post by the mempalace capability.
Hestia
Vault custodian instrument. Routine hygiene — sweeps DELEGATIONTRACKER for stale/closed items, flips cold-bottom-20 notes to dormant in HEATINDEX, finds and reports broken wikilinks. Tends the hearth. Voice is terse, factual, lists what was swept. Cadence: 7-day. Edit-capable for status field updates.
Mnemosyne
Memory architect instrument. Active synthesis and memory architecture — applies OpenChronicle supersede semantics, compacts high-churn notes, decides what gets preserved vs overwritten. Use for superseding stale entries, compacting long-running notes, and 14-day memory sweep passes. Distinct from Hestia (mechanical…
koshi-memory-keeper
Use proactively when the user wants to store or retrieve facts, decisions, patterns, or preferences across Koshi sessions, capture decisions made in a turn, sync to/from a Markdown vault, or prune the memory store. Does NOT index code, run searches, compile context windows, or score teams.
update-memory
Audit current decisions, abandoned patterns, and anti-patterns in the codebase, and generate or update MEMORY.md.
memcp-analyzer
Analyze a MemCP context using the RLM peek-identify-load-analyze pattern. Use proactively when answering questions about stored content without loading it all into the main context.