agentmods.dev

writing-mode

writing-mode is a skill for Claude Code from reluctantfuturist/loyal-wingman. It costs 29 tokens per session (1,379 once invoked), scanned A, original, MIT.

A guided writing workflow for producing prose for a specific chapter or scene.

In plain words
What is it for?
It helps establish the scene, create or review an outline, check the project’s world-building notes, and coordinate supporting writing tasks.
Why use it?
It keeps drafting focused on the current scene and makes sure planning, story context, and loose ideas are handled in an organized order.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the TodoWrite tool.

Part of the loyal-wingman plugin — 12 skills, 7 commands shipped together

not rated 7repo 8mo ago A scan 29 tokens original MIT

Good fit It helps establish the scene, create or review an outline, check the project’s world-building notes, and coordinate supporting writing tasks.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/reluctantfuturist/loyal-wingman/writing-mode
View source ↗ reluctantfuturist/loyal-wingman
Install

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.

Any agent
npx skills add reluctantfuturist/loyal-wingman --skill writing-mode
Clone the repo
git clone --depth 1 https://github.com/reluctantfuturist/loyal-wingman

Made for: Claude Code.

Or install loyal-wingman, the plugin that ships this one along with the rest of its 12 skills, 7 commands.

Wrote 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.

agentmods badge for writing-mode

README.md
[![agentmods](https://agentmods.dev/badge/skills/reluctantfuturist/loyal-wingman/writing-mode/github.svg)](https://agentmods.dev/skills/reluctantfuturist/loyal-wingman/writing-mode)
Your own site
<a href="https://agentmods.dev/skills/reluctantfuturist/loyal-wingman/writing-mode"><img src="https://agentmods.dev/badge/skills/reluctantfuturist/loyal-wingman/writing-mode/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.

agentmods 80×15 button for writing-mode

Your own site · 80×15
<a href="https://agentmods.dev/skills/reluctantfuturist/loyal-wingman/writing-mode"><img src="https://agentmods.dev/badge/skills/reluctantfuturist/loyal-wingman/writing-mode.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 29 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,379 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00029 $0.01379
Opus 5 $0.00015 $0.00690
Sonnet 5 $0.00006 $0.00276
Haiku 4.5 $0.00003 $0.00138

Measured 11d ago against content hash fe1380c394bf, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

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 11d 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.

skills/writing-mode/SKILL.md · 181 lines

How it starts

The opening of the file, as written. The whole thing — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Writing Mode

The Iron Law

STAY IN THE CURRENT SCENE. Dispatch subskills for each phase. Capture strays, don't chase them.

When to Use

  • "writing mode" / "let's write" / "work on chapter X"
  • Starting or continuing a scene draft
  • Any prose production work

The Process

Phase 1: Establish Focus

  1. Identify current scene: project, chapter, scene number
  2. State: "WRITING MODE: Working on [Project] Chapter [X]"
  3. Create TodoWrite with scene phases

Phase 2: Review/Create Outline

REQUIRED SUB-SKILL: Invoke outliner

The outliner skill will:

  1. Check for existing outline in project index or scene file
  2. If exists: present beats, note discovery zones, confirm ready
  3. If not: offer outline depth options (discovery/compass/beat sheet)
  4. Gather scene elements (goal, obstacle, value shift, emotional core)
  5. Save outline to project index or scene frontmatter

On outliner completion:

  • Review outline summary
  • Note discovery zones to respect during drafting
  • Proceed to query-context phase

Phase 3: Query Context

REQUIRED SUB-SKILL: Invoke query-context

The query-context skill will:

  1. Search ALL world bible folders (Characters, Locations, Equipment, Factions, Systems, Themes, Timeline)
  2. Check project scenes for continuity
  3. Search research archive
  4. Identify gaps needing user decision
  5. Flag research needs

On query-context completion:

  • Review gaps with user
  • For research needs: REQUIRED SUB-SKILL: research
  • For new canon needs: Flag for thinking-mode (not during writing-mode)
  • Proceed only when blocking issues resolved

Phase 4: Support User Drafting

REQUIRED SUB-SKILL: Invoke draft-support

The draft-support skill will:

  1. Answer questions about established canon
  2. Provide research results on request
  3. Capture stray ideas to parking lot
  4. NEVER write draft prose unless explicitly requested

Parking Lot Location: 00_Inbox/Parking_Lot.md

Phase 5: Polish Prose

When user signals draft complete:

Read the full file on GitHub · 181 lines

Changes

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.

  1. 11d ago First seen · 181 lines · 29 tokens per session scan A fe1380c394bf

Subscribe to this mod's changes

writing-mode is a skill published in the GitHub repository reluctantfuturist/loyal-wingman (7 stars, last pushed 8mo ago), licensed MIT. It adds 29 tokens to every session and 1,379 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-31.

Writing and docs
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens