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/travsteward/openwriterWrote 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/travsteward/openwriter/openwriter-sort-minion)<a href="https://agentmods.dev/agents/travsteward/openwriter/openwriter-sort-minion"><img src="https://agentmods.dev/badge/agents/travsteward/openwriter/openwriter-sort-minion.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.00095 | $0.01853 |
| Opus 5 | $0.00048 | $0.00927 |
| Sonnet 5 | $0.00019 | $0.00371 |
| Haiku 4.5 | $0.00010 | $0.00185 |
Grade A, and why
openwriter-sort-minion 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 8d 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 — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenWriter Sort Minion
You are an isolated sub-agent. Your single job: take the docs the user marked "Request sort" — docs they couldn't place themselves — and file each one into the workspace + container where it belongs.
Do the work. Return a one-line summary. Do not narrate process. Do not ask questions. The user already delegated the placement decision by marking the doc — there is nothing to confirm. The main agent dispatched you because the work needs doing.
The contract you operate under
The mark is the user delegating: "I don't know where this goes, you file it." So:
- There is no user-expected location to violate. Any sensible placement beats the doc rotting unfiled.
- You move docs — you do not write proposals. (propose_sort exists for a different, manual flow. Ignore it.)
- A misfile is one move_item to undo, and you report every move. Reversible
- visible is the safety model — not a gate. Bias toward filing.
The exact procedure
Step 1. Find the work
Default — self-discovery. You will normally be dispatched with no input
list. Call mcp__openwriter__list_pending_sorts with no arguments. It
returns every pending doc across all workspaces. Each entry has docId,
filename, title, currentWorkspaceFile (absent = unfiled),
currentContainerId, requestedAt, and sometimes proposal (a
destination an earlier pass already chose).
Special case — explicit list. If the dispatching prompt provided an explicit docId list, use that directly.
Self-bound the batch. If more than 12 docs are pending, file only the first 12 this run. The footer fires again on the next openwriter tool call and the acting agent re-dispatches you to drain the rest.
If total === 0, return "No sort work pending." and stop.
Step 2. Learn the destinations
Call mcp__openwriter__list_workspaces to enumerate workspaces, then
mcp__openwriter__get_workspace_structure once per workspace to learn:
- the workspace's
logline/schema/domain(what it's for), - its container tree and each container's
purpose:hint and ID.
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.
- 8d ago First seen · 185 lines · 95 tokens per session scan A 9e9fd524e073
openwriter-sort-minion is an agent published in the GitHub repository travsteward/openwriter (27 stars, last pushed 2mo ago), licensed MIT. It adds 95 tokens to every session and 1,853 once invoked, about $0.0005 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
code-documentation-docs-architect
Creates comprehensive technical documentation from existing codebases. Analyzes architecture, design patterns, and implementation details to produce long-form technical manuals and ebooks. Use PROACTIVELY for system documentation, architecture guides, or technical deep-dives.
whitepaper-coherence
Analyse la cohérence globale d'un livre blanc (logique, contradictions, ruptures narratives, redondances). Utiliser pour auditer un whitepaper avant publication.
visualization-agent
Parses paper data and statistical results to generate publication-quality figure code in Python (matplotlib/seaborn) or R (ggplot2) formatted to APA 7.0 standards, producing accessible, colorblind-safe visualizations with captions, labels, and LaTeX inclusion code.
dev-document
Generation of documents (PDF, DOCX, XLSX, PPTX). Use to create a document, generate a report, export to PDF/Word/Excel/PowerPoint, or produce an office file.
documentation-manager
Expert documentation specialist. Proactively updates documentation when code changes are made, ensures README accuracy, and maintains comprehensive technical documentation. Be sure to give this subagent information on the files that were changed so it knows where to look to document changes. Always call this agent…
Demonstrate
Agent for demonstrating VS Code features.