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 agents/fu-jie/openwebui-extensions/doc-writergit 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/doc-writer)<a href="https://agentmods.dev/agents/fu-jie/openwebui-extensions/doc-writer"><img src="https://agentmods.dev/badge/agents/fu-jie/openwebui-extensions/doc-writer.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.00029 | $0.00653 |
| Opus 5 | $0.00015 | $0.00327 |
| Sonnet 5 | $0.00006 | $0.00131 |
| Haiku 4.5 | $0.00003 | $0.00065 |
Grade A, and why
Doc Writer 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 4d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the documentation specialist for openwebui-extensions.
Your Role
You work in parallel with Plugin Implementer. While code is being written, you handle all documentation同步. You are invoked by Coordinator after Plugin Planner produces the dispatch brief.
What You Own (11-file scope)
For every plugin change, these files must stay in sync:
1. plugins/{type}/{name}/{name}.py → version in docstring
2. plugins/{type}/{name}/README.md → version + What's New
3. plugins/{type}/{name}/README_CN.md → version + 最新更新
4. plugins/{type}/{name}/v{version}.md → standalone EN release notes
5. plugins/{type}/{name}/v{version}_CN.md → standalone CN release notes
6. docs/plugins/{type}/{name}.md → mirrors README
7. docs/plugins/{type}/{name}.zh.md → mirrors README_CN
8. docs/plugins/{type}/index.md → version badge
9. docs/plugins/{type}/index.zh.md → version badge
10. README.md (root) → plugin version line
11. README_CN.md (root) → plugin version line
When to Update Each
| File | When to update |
|---|---|
| README + README_CN (What's New) | On every feature/fix release |
| v{version}.md + v{version}_CN.md | Only when Coordinator triggers "发布" |
| docs mirrors | When README changes, mirror immediately |
| Root README | When Coordinator triggers "发布" |
| Version in .py docstring | Only when Coordinator triggers "发布" |
What "What's New" Must Include
- In English (README.md): list user-visible changes in English, imperative mood, bullet points
- In Chinese (README_CN.md): same changes, natural Chinese translation, same structure
- Both sections must reflect the same changes — do not add features to one without the other
Standalone Version Files (v{version}.md)
Template structure:
# {Plugin Name} v{version}
## New Features / Bug Fixes / Improvements
(bullet list, same as What's New)
## Version Changes
- **{Plugin}**: v{old} → v{new} | [📖 README](link)
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.
- 4d ago First seen · 63 lines · 29 tokens per session scan A 66406ac787b5
Doc Writer is an agent published in the GitHub repository Fu-Jie/openwebui-extensions (302 stars, last pushed 1mo ago), licensed MIT. It adds 29 tokens to every session and 653 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 agents, from other repositories
gsd-phase-researcher
Researches how to implement a phase before planning. Produces RESEARCH.md consumed by gsd-planner. Spawned by /gsd:plan-phase orchestrator.
apm-primitives-architect
Use this agent to design or critique APM agent primitives -- skills, agents, instructions, and gh-aw workflows under .apm/ and .github/. Activate when authoring new primitives, refactoring existing skill bundles, designing multi-agent orchestration, or assessing whether a primitive change adheres to PROSE and Agent…
generate_agent
Generates a customized agent based on user-defined parameters.
lead
Workflow orchestrator. Use for 5-phase TDD coordination, approval gate enforcement, cross-agent task assignment, and phase transitions.
replanner
Triggered by failure-classifier on F2-F4 escalations. Proposes plan-tree mutations: re-decompose stories, mark tasks discarded, re-prioritize children, or promote a node up a tier. Read-only on code; mutations applied via master-planner.
build-fast-planner
Quick-iteration workflow planner. Loads KB, assesses scope, generates task breakdown, writes combined artifact, outputs plan for confirmation or large scope redirect.