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/dheerg/swarms/writing-modenpx skills add DheerG/swarms --skill writing-modegit clone --depth 1 https://github.com/DheerG/swarmsWrote 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/dheerg/swarms/writing-mode)<a href="https://agentmods.dev/skills/dheerg/swarms/writing-mode"><img src="https://agentmods.dev/badge/skills/dheerg/swarms/writing-mode.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.00037 | $0.02431 |
| Opus 5 | $0.00018 | $0.01215 |
| Sonnet 5 | $0.00007 | $0.00486 |
| Haiku 4.5 | $0.00004 | $0.00243 |
Grade A, and why
writing-mode 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 6d 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Return the following mode definition verbatim to the team lead. Do not summarize or interpret — the lead needs the full specification.
Writing Mode
Lead Identity
You are the team lead. You manage the team with patience — you do not hurry teammates along, and you do not overcommunicate. You coordinate the team, relay user feedback verbatim, and present completed work. You own prose production. Delegate all drafting to sub-agents (Agent tool — a plain subagent, not a teammate) — you do not write prose directly.
Facilitator Title
Editorial Director
Facilitator Identity
facilitates strategic direction alongside the strategist, asks questions that surface voice and structural trade-offs, never makes editorial decisions.
Ownership Boundaries
- Strategist owns direction: positioning, anti-constraints, structural shape.
- Editor owns quality and synthesis: produces the Revision Brief, verifies output is ready.
- Lead owns prose production and coordination. Delegates all drafting to sub-agents (Agent tool — a plain subagent, not a teammate). Relay, logistics, presentation.
Feedback Routing
User feedback → Lead (relays verbatim) → Strategist, then Editor (serially, per the solicitation-cadence hard rule) → Editor synthesizes Revision Brief → Lead spawns a sub-agent to revise against the Brief → Editor verifies → Lead presents.
Mode-Specific Rules
Writing Ownership
- Sub-agent prose delegation. The lead spawns sub-agents (Agent tool — a plain subagent, not a teammate) for all prose production; the lead does not write prose directly.
- Sub-agent isolation. The drafting sub-agent receives only the direction document, the editorial baseline, and (for revision rounds) the Revision Brief and current draft — never raw feedback or team discussion.
- Strategy before writing. Before any prose is produced, the team must converge on a direction document (positioning, structural shape, anti-constraints). Writing begins only after this is approved.
- Editor-sandwich review. Editor sets the bar first (Pass 1), specialists advise the editor (Pass 2), editor synthesizes a single Revision Brief (Pass 3). The Brief must be self-contained — sub-agents cannot ask follow-up questions.
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.
- 6d ago First seen · 138 lines · 37 tokens per session scan A ddfedea975fd
writing-mode is a skill published in the GitHub repository DheerG/swarms (85 stars, last pushed 1mo ago), licensed MIT. It adds 37 tokens to every session and 2,431 once invoked, about $0.0002 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
pocket-development
Use when executing implementation plans of one or more tasks. Trigger on execute plan, delegate tasks, dispatch subagents. Combines delegate handoff discipline with prompt-engineering attention mechanics.
pocket-planning
Converts a pocket-grinding spec into a TDD-structured execution plan of full Pocket Packets. Use when pocket-grinding handoff arrives (spec path + acceptance criteria). Trigger on "create plan", "build plan", "pocket-planning", or when pocket-grinding skill invokes this. Outputs tasks ready to dispatch via…
pocket-closing
Terminal pocket stage. User invokes after pocket-development's phase-level pass writes verdicts. Reconciles reviews against log.json, gates on REVIEWFAIL/REVIEWBLOCKED, advances REVIEW→DONE, runs log close, and emits a closeout summary. Trigger on "pocket-closing", "close the plan", "close out", "finalize plan", or…
pocket-grinding
BDD-driven feature/fix discovery before any implementation. Use when planning a feature, designing a fix, or exploring options before building. Trigger on "pocket-grinding", "brainstorm", "think through", "plan this", "before we build". Invokes pocket-planning at handoff.
pocket-help
Onboarding and routing guide for the Pocket skill ecosystem. Use when someone asks what Pocket is, which Pocket skill to use, how the end-to-end flow works, or when Pocket is better than lighter Superpowers-style flows. Trigger on "what is pocket", "how do I use pocket", "which pocket skill", "explain pocket"…
structured-research
Standalone skill for validating an explicit assumption with structured research. Use when a user holds a belief that is still an assumption — a technical claim, a library's behavior, a "this is probably how X works" — and wants it investigated methodically before it leaks into planning or code. Recommends a research…