blog-outline

blog-outline is a command for Claude Code from Amey-Thakur/AI-SKILLS. It costs 22 tokens per session (359 once invoked), scanned A, original, MIT.

A planning command that creates a detailed outline for a blog post before drafting. The outline covers the title, main argument, opening, sections, supporting examples, and conclusion.

In plain words
What is it for?
It is for turning a topic, audience, and angle into a usable blog-post outline.
Why use it?
It gives the writer a clear structure and single main point before writing begins. This reduces the need to invent the argument and order while drafting.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter.

Good fit It is for turning a topic, audience, and angle into a usable blog-post outline.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/amey-thakur/ai-skills/blog-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.

Clone the repo
git clone --depth 1 https://github.com/Amey-Thakur/AI-SKILLS

Made for: Claude Code.

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

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/amey-thakur/ai-skills/blog-outline"><img src="https://agentmods.dev/badge/commands/amey-thakur/ai-skills/blog-outline.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 22 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 359 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.00022 $0.00359
Opus 5 $0.00011 $0.00179
Sonnet 5 $0.00004 $0.00072
Haiku 4.5 $0.00002 $0.00036

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

Security

Grade A, and why

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

commands/blog-outline.md · 39 lines

What it actually says

You were invoked as a slash command. The user's input:

$ARGUMENTS

Use that input to fill this prompt's variables (take the main content, topic, or task from it; ask only if a required value is missing and not supplied), then follow the prompt exactly.


Outline a blog post on: {topic}

Audience and takeaway: {audience} Angle: {angle}

Produce:

  • A working title (and 2 alternates) that promises a specific value.
  • The one main point the post makes (the thesis). A post that makes one point well beats one that surveys everything.
  • The hook idea for the intro: how to open so the reader keeps reading (a concrete problem, a surprising claim, a question they feel).
  • The section flow: each section as a heading plus the key points under it, in an order that builds the argument or walks the reader through. Enough detail that writing each section is filling in, not inventing.
  • Where examples, data, or visuals go (the parts that make it credible and concrete).
  • The takeaway/close: what the reader leaves with and any call to action.

Rules: get the structure and angle right before drafting (a strong outline is most of the work). One throughline, not a grab-bag. Match scope to the audience and format. Flag if the topic is too broad (suggest narrowing) or too thin (suggest what would fill it). Ask about tone or any facts only I have if it shapes the outline.

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 · 39 lines · 22 tokens per session scan A 351ad3876b42

Subscribe to this mod's changes

blog-outline is a command published in the GitHub repository Amey-Thakur/AI-SKILLS (7 stars, last pushed 6d ago), licensed MIT. It adds 22 tokens to every session and 359 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.