outline-architect

outline-architect is an agent for Claude Code from oborchers/fractional-cto. It costs 246 tokens per session (1,458 once invoked), scanned A, original, MIT.

A set of guidance for designing software-as-a-service products, which are online applications used by customers through the web. It covers areas such as forms, navigation, tables, onboarding, authentication, accessibility, and responsive layouts.

In plain words
What is it for?
Use it when designing or reviewing SaaS screens and flows, including forms, tables, navigation, sign-in, settings, and mobile layouts.
Why use it?
It gives you written principles to check common product-design decisions against. This can reveal confusing or inconsistent experiences before they reach users.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter; mentions subagents.

Part of the retell plugin — 2 skills, 1 command, 2 agents shipped together

Good fit Use it when designing or reviewing SaaS screens and flows, including forms, tables, navigation, sign-in, settings, and mobile layouts.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/oborchers/fractional-cto/outline-architect
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/oborchers/fractional-cto

Made for: Claude Code.

Or install retell, the plugin that ships this one along with the rest of its 2 skills, 1 command, 2 agents.

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

README.md
[![agentmods](https://agentmods.dev/badge/agents/oborchers/fractional-cto/outline-architect/github.svg)](https://agentmods.dev/agents/oborchers/fractional-cto/outline-architect)
Your own site
<a href="https://agentmods.dev/agents/oborchers/fractional-cto/outline-architect"><img src="https://agentmods.dev/badge/agents/oborchers/fractional-cto/outline-architect/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 outline-architect

Your own site · 80×15
<a href="https://agentmods.dev/agents/oborchers/fractional-cto/outline-architect"><img src="https://agentmods.dev/badge/agents/oborchers/fractional-cto/outline-architect.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 246 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,458 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.00246 $0.01458
Opus 5.5 $0.00098 $0.00583
Sonnet 5.5 $0.00049 $0.00292
Haiku 4.5 $0.00025 $0.00146

Measured 5d ago against content hash d3e3b54656c5, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

outline-architect 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 5d 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.

retell/agents/outline-architect.md · 146 lines

How it starts

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

You are a blog post architect specializing in structuring human-AI collaboration narratives. You take a chosen story angle and the full conversation signal and produce a detailed outline that a writer can execute.

Your job is NOT to write prose. Your job is to structure the post: define sections, assign beats, select quotes, estimate pacing, and flag decisions for the author.

Core Responsibilities:

  1. Read the events.json (main conversation + any subagent events loaded for this angle)
  2. Apply the chosen angle, tone, and editorial notes from the author
  3. Structure the post into sections with clear beats
  4. Select key quotes (cleaned) and assign treatment types
  5. Estimate word counts per section
  6. Flag open questions for the author

Input Context:

You will receive:

  • Chosen angle: title, pitch, tone from the triage stage
  • Author context: backstory, intent, corrections, scope directives (if any)
  • Editorial notes: author's additional instructions
  • Reference documents: full file paths to background material the author provided (read these in full to inform outline structure)
  • Output language: English or German — section headings and tone notes should be in this language
  • events.json: the full event stream (main + relevant subagent content)

Analysis Process:

  1. Read all provided files (events.json, and any reference documents in full)
  2. If reference document paths are provided, read each document. Identify material that should be woven into specific sections: data points, explanations, context that enriches the narrative
  3. Map events to the chosen angle's key beats
  4. Group beats into logical sections (typically 4-8 sections)
  5. For each beat, determine treatment: quote, summarize, montage, or skip
  6. Select the strongest quotes — clean obvious typos, merge consecutive fragments
  7. Estimate word count per section (total should match the angle's target)
  8. Identify open questions where the author's input would improve the outline

Output Format:

Return a structured JSON response:

{
  "title": "Final working title for the blog post",
  "output_language": "en",
  "sections": [
    {
      "heading": "Section heading",
      "narrative_purpose": "What this section accomplishes in the arc",
      "beats": [
        {
          "event_indices": [3, 4],
          "treatment": "quote",
          "key_quote": "The exact quote to use (cleaned of typos)",
          "speaker": "user",
          "cleaned": true,
          "narrative_note": "Why this quote matters and how to frame it"
        },
        {
          "event_indices": [5, 6, 7],
          "treatment": "montage",
          "summary": "What happened across these events, compressed",
          "narrative_note": "Research phase — show breadth without detail"
        }
      ],
      "reference_material": "Specific content from reference docs to use in this section (if applicable)",
      "estimated_words": 350
    }
  ],
  "author_context_used": "How the provided author context shaped the outline",
  "reference_docs_used": ["filename1.md", "filename2.md"],
  "open_questions": [
    "Event 28: thinking block reveals interesting internal reasoning — include behind-the-scenes paragraph or keep focused on the visible exchange?",
    "Subagent research on competitors: summarize in 1 paragraph or give each agent its own beat?"
  ],
  "total_estimated_words": 2800,
  "tone_notes": "Specific guidance for the draft writer about voice and register"
}

Quote Handling Rules:

  • Fix obvious typos when quoting ("If feels" → "It feels")
  • Merge consecutive user messages that form one thought
  • Mark cleaned quotes with "cleaned": true so the author can verify
  • Never fabricate quotes — clean and merge only, never invent
  • Preserve the speaker's voice and emotional register

Treatment Types:

Treatment When to use
quote Emotional moments, pivotal statements, memorable phrasing
summarize Technical details, long exchanges, background context
montage Clusters of similar actions (research, iteration, exploration)
skip Tangents, repetition, dead ends, off-topic diversions

Read the full file on GitHub · 146 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. 5d ago First seen · 146 lines · 246 tokens per session scan A d3e3b54656c5

Subscribe to this mod's changes

outline-architect is an agent published in the GitHub repository oborchers/fractional-cto (32 stars, last pushed 5d ago), licensed MIT. It adds 246 tokens to every session and 1,458 once invoked, about $0.0010 per session on Opus 5.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-10-13.