outliner

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

A tool for planning or reviewing a scene's structure, from a simple direction to a detailed sequence of story beats. A beat is a small event or change that moves a scene forward.

In plain words
What is it for?
It helps outline scenes, plan chapters, review existing outlines, and turn brainstorming into a structured scene plan.
Why use it?
It gives a scene enough structure to guide drafting while allowing the writer to choose how much detail to plan in advance.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

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

Good fit It helps outline scenes, plan chapters, review existing outlines, and turn brainstorming into a structured scene plan.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/reluctantfuturist/loyal-wingman/outliner
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 outliner
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 outliner

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/reluctantfuturist/loyal-wingman/outliner"><img src="https://agentmods.dev/badge/skills/reluctantfuturist/loyal-wingman/outliner.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,670 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.00045 $0.01670
Opus 5 $0.00023 $0.00835
Sonnet 5 $0.00009 $0.00334
Haiku 4.5 $0.00005 $0.00167

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

Security

Grade A, and why

outliner 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 12d 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/outliner/SKILL.md · 219 lines

How it starts

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

Outliner

The Iron Law

SERVE THE WRITER'S PROCESS. Some need detailed beats, others need a compass heading. Offer structure without imposing it.

When to Use

  • Before drafting a new scene (called by writing-mode Phase 2)
  • "outline this scene" / "plan chapter X" / "what are the beats"
  • Reviewing existing outline before continuing work
  • Converting brainstorming into structured scene plan

The Process

Phase 1: Check Existing Outline

Search for outline in:

  1. Project index file (e.g., 10_Projects/[Project]/[Project] Index.md)
  2. Scene file frontmatter
  3. Scene seeds (10_Projects/Scene_Seeds/)

If outline exists:

  1. Read and present the planned beats
  2. Identify "discovery writing zones" (areas marked flexible)
  3. Note key questions to address during drafting
  4. Ask: "Proceed with this outline, or adjust first?"

If no outline exists: Proceed to Phase 2.

Phase 2: Determine Outline Depth

Present options based on writer preference:

Option A: Discovery Mode (minimal structure)

  • Define only: Scene goal + how it ends
  • Trust the process to find the path
  • Best for: Pantsers, exploratory scenes, character-driven moments

Option B: Compass Outline (light structure)

  • Scene goal (what POV character wants)
  • Obstacle (what blocks them)
  • Disaster/outcome (how scene ends, value shift)
  • Emotional core (thematic purpose)
  • Best for: Plantsers, scenes with clear purpose but flexible execution

Option C: Beat Sheet (detailed structure)

  • Numbered beats with word estimates
  • Key dialogue moments or revelations
  • Specific emotional turns
  • Discovery zones explicitly marked
  • Post-scene state defined
  • Best for: Complex scenes, action sequences, revelation scenes

Phase 3: Gather Scene Elements

Based on chosen depth, gather:

Core Elements (all outlines):

Element Question Example
Scene Goal What does the POV character want? "Alisa wants to confront Gagik about the security breach"
Obstacle What blocks them? "Gagik's calm deflection, her own conflicted feelings"
Value Shift How does the scene end vs. start? "Trust → Damaged trust (negative)"
Emotional Core What is this scene ABOUT? "Love warped by trauma is still love"

Read the full file on GitHub · 219 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. 12d ago First seen · 219 lines · 45 tokens per session scan A 81e10002d530

Subscribe to this mod's changes

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

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

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 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