draft

A content-writing workflow that turns a stored idea into a draft for formats such as tweets, threads, LinkedIn posts, blog articles, or video scripts. It uses a “Shipping Bible,” a set of writing principles and templates.

In plain words
What is it for?
Use it to browse ideas, select one, and create a dated Markdown draft with a hook, story, key points, call to action, and launch checklists.
Why use it?
It removes the need to choose an idea, format, structure, and checklist from scratch. It gives unfinished ideas a consistent place and shape.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/railly/agent-brain/draft
Any agent
npx skills add Railly/agent-brain --skill draft
Clone the repo
git clone --depth 1 https://github.com/Railly/agent-brain

Made for: Claude Code, Codex.

Per session 11 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 908 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00011 $0.00908
Opus 5 $0.00005 $0.00454
Sonnet 5 $0.00002 $0.00182
Haiku 4.5 $0.00001 $0.00091

Measured yesterday against content hash 29aad8f15b4d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

draft 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 yesterday.

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.

.agents/skills/draft/SKILL.md · 156 lines

How it starts

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

Create content draft: $ARGUMENTS

Philosophy

  • Ship > Perfect
  • Build in public
  • Story > Features
  • Time-box everything

IMPORTANT: Be direct

  • Don't check if folders exist
  • Just create the draft

Flow

  1. Show available ideas from 05_Areas/content-creation/ideas/

    • List ideas with source notes
    • Ask which to draft (or use $ARGUMENTS if specified)
  2. Determine content type:

    • Tweet (single post)
    • Thread (multi-post story)
    • LinkedIn (longer story format)
    • Blog (full article)
    • Video script (demo/tutorial)
  3. Create draft in 06_Content/{{YYYY-MM-DD}}/{slug}/{type}.md:

    ---
    type: {tweet|thread|linkedin|blog|video}
    status: draft
    created: {{date}}
    source: [[{source-note}]]
    publish_date:
    ---
    # {Title}
    
    ## Hook
    {First line that grabs attention}
    
    ## Story
    {What + Why + How long it took}
    
    ## Key Points
    - {Point 1}
    - {Point 2}
    - {Point 3}
    
    ## CTA
    {What do you want them to do?}
    
    ## Draft
    {Actual content here}
    
    ---
    ## Pre-Launch Checklist
    - [ ] Teaser posted (24-48h before)
    - [ ] WIP shots shared
    - [ ] 3-5 people ready to engage
    - [ ] Demo video recorded (if applicable)
    - [ ] Captions added (video)
    
    ## Launch Checklist
    - [ ] Posted on primary platform
    - [ ] Cross-posted
    - [ ] Shared in communities
    - [ ] Responded to comments (first 2h)
    
    ## Post-Launch
    - [ ] Wins captured
    - [ ] Feedback noted
    - [ ] Retro done
    
  4. Generate draft content based on type:

    Tweet:

    {Hook - one punchy line}
    
    {2-3 key points}
    
    {CTA + link}
    

    Thread:

    1/ {Hook}
    2/ {Context/Why}
    3/ {What I built}
    4/ {Key learning 1}
    5/ {Key learning 2}
    6/ {Demo/Screenshot}
    7/ {CTA}
    

    LinkedIn:

    I just built [THING] in [TIME].
    
    Here's what it does:
    → {Feature 1}
    → {Feature 2}
    → {Feature 3}
    
    Why I built it:
    {1-2 sentences}
    
    What I learned:
    {Key insight}
    
    Try it: [LINK]
    Star it: [GITHUB]
    
    #buildinpublic
    

Read the full file on GitHub · 156 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. yesterday First seen · 156 lines · 11 tokens per session scan A 29aad8f15b4d

Subscribe to this mod's changes

draft is a skill published in the GitHub repository Railly/agent-brain (22 stars, last pushed 1mo ago), licensed MIT. It adds 11 tokens to every session and 908 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

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

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 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

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