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 skills/dromologue/workflowymcp/wflownpx skills add dromologue/workflowyMCP --skill wflowgit clone --depth 1 https://github.com/dromologue/workflowyMCPWhat 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.00095 | $0.20644 |
| Opus 5 | $0.00048 | $0.10322 |
| Sonnet 5 | $0.00019 | $0.04129 |
| Haiku 4.5 | $0.00010 | $0.02064 |
Grade A, and why
wflow 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 2d 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 — 756 lines — stays where its author put it; the contents beside it link to each section on GitHub.
wflow — second-brain skill (template)
This is the generic skill template shipped by the workflowy-mcp-server repo. It deliberately contains no user-specific node IDs — those live in $SECONDBRAIN_DIR/memory/workflowy_node_links.md. On first use, walk the user through populating that file (see Bootstrap below).
The skill spans the full second-brain loop:
- Capture — tasks, links, ink, reading material.
- Triage and prioritisation — daily / weekly / monthly cascade.
- Synthesis — distillation of reading and conversation into atomic notes.
- Retrieval — graph queries across Workflowy and any additional services the user has configured.
It is invoked conversationally — the user does not need to type slash commands. Match by intent, not by exact wording.
Which surface am I on
Up to four MCP surfaces can reach the same Workflowy account: this server over stdio on the user's machine (mcp__workflowy__*), the WorkFlowy CLI (mcp__workflowy-cli__*, if wf is installed and wired in), WorkFlowy's own desktop MCP inside the desktop app (mcp__workflowy-desktop__*), and — if the user has deployed one — a remote connector for claude.ai web/mobile and cloud sandboxes, which is this same server behind an HTTP shim. Decide by device first, then by capability.
Decide in one line. On the user's machine, route reads, searches and ordinary writes to a native surface (the CLI, or the desktop MCP when the app is running) and come to this server for method work — mirror discipline,
review, anything touching$SECONDBRAIN_DIR, anything scheduled. Never use a remote connector from a machine that can reach this server: they share one Workflowy account and therefore one API rate limit, so local traffic routed remotely burns the quota the mobile and cloud surfaces depend on. If a native surface is unavailable, fall back to this server automatically; never fall outward to the connector.
Native first for lookups and ordinary writes (changed 2026-08-17). Earlier versions of this skill said to prefer this server unless the task needed attachments or client navigation. That is now wrong, and following it wastes API quota on work a native surface does better and for free.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 756 lines · 95 tokens per session scan A 4f6898605b50
wflow is a skill published in the GitHub repository dromologue/workflowyMCP (10 stars, last pushed 12d ago), licensed MIT. It adds 95 tokens to every session and 20,644 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.