topic-outline

topic-outline is a skill for Claude Code, Codex from xiaotianfotos/homerail. It costs 28 tokens per session (326 once invoked), scanned A, original, MIT.

A skill for creating and revising structured topic outlines from a brief, audience, angle, thesis, sections, questions, and sources. It is intended for editorial planning rather than a software task checklist.

In plain words
What is it for?
Use it to plan or revise articles and other content topics, including their structure, supporting sources, open questions, and editorial direction.
Why use it?
It keeps an evolving content plan organized while preserving known information and separating unresolved decisions. It also records the next useful writing step and confidence level.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to plan or revise articles and other content topics, including their structure, supporting sources, open questions, and editorial direction.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/xiaotianfotos/homerail/topic-outline
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 xiaotianfotos/homerail --skill topic-outline
Clone the repo
git clone --depth 1 https://github.com/xiaotianfotos/homerail

Made for: Claude Code, Codex.

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 topic-outline

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/xiaotianfotos/homerail/topic-outline"><img src="https://agentmods.dev/badge/skills/xiaotianfotos/homerail/topic-outline.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 28 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 326 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00028 $0.00326
Opus 5 $0.00014 $0.00163
Sonnet 5 $0.00006 $0.00065
Haiku 4.5 $0.00003 $0.00033

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

Security

Grade A, and why

topic-outline 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 13d 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.

plugins/builtin/topic-outline/skills/topic-outline/SKILL.md · 22 lines

What it actually says

Topic Outline

Use this Skill when the user asks to plan, structure, or revise a content topic. Do not use it for a generic task checklist or for an outline the user did not request.

Call the current Tool catalog entry for com.homerail.topic-outline:upsert_topic_outline with the complete current outline. Its harness-safe wire name is supplied by the current turn and must not be guessed. Reuse one stable plugin-owned id such as com.homerail.topic-outline:current across turns so a revision replaces the same semantic node without colliding with Core or another plugin. A partial outline is valid: record what is known, preserve useful prior fields, and put only unresolved decisions in questions.

Keep the shape concise:

  • title names the topic, not the UI component.
  • brief, audience, angle, and thesis capture the current editorial direction.
  • outline contains ordered sections with short points and truthful status.
  • sources includes only real HTTP(S) references supplied or found through an authorized tool.
  • next_action states the next useful editorial step.
  • confidence reflects evidence, not presentation polish.

Use the matching topic-outline Tool only when it is listed for the current turn. Do not substitute a legacy dynamic widget. If the requested outline is not placed on the canvas, tell the user only that visible result and offer to retry.

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. 13d ago First seen · 22 lines · 28 tokens per session scan A adf98236a91a

Subscribe to this mod's changes

topic-outline is a skill published in the GitHub repository xiaotianfotos/homerail (951 stars, last pushed today), licensed MIT. It adds 28 tokens to every session and 326 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-30.

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