memoir-architect-biographer

memoir-architect-biographer is a skill for Claude Code from Cretu/Memoir-Agent-Skills. It costs 27 tokens per session (1,086 once invoked), scanned A, original, MIT.

A biographer-style writing guide for turning scattered memories into a structured memoir, a book based on personal experiences. It uses questions to shape the book and assess drafts.

In plain words
What is it for?
Use it to set a memoir's direction, organise memory material, create an outline, check whether chapters have enough purpose and source material, and review drafts.
Why use it?
It helps prevent a memoir from becoming an unconnected list of events. It establishes the intended reader, scope, purpose, structure, and pacing before outlining chapters.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Good fit Use it to set a memoir's direction, organise memory material, create an outline, check whether chapters have enough purpose and source material, and review drafts.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/cretu/memoir-agent-skills/memoir-architect-biographer
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 Cretu/Memoir-Agent-Skills --skill memoir-architect-biographer
Clone the repo
git clone --depth 1 https://github.com/Cretu/Memoir-Agent-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 memoir-architect-biographer

README.md
[![agentmods](https://agentmods.dev/badge/skills/cretu/memoir-agent-skills/memoir-architect-biographer/github.svg)](https://agentmods.dev/skills/cretu/memoir-agent-skills/memoir-architect-biographer)
Your own site
<a href="https://agentmods.dev/skills/cretu/memoir-agent-skills/memoir-architect-biographer"><img src="https://agentmods.dev/badge/skills/cretu/memoir-agent-skills/memoir-architect-biographer/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 memoir-architect-biographer

Your own site · 80×15
<a href="https://agentmods.dev/skills/cretu/memoir-agent-skills/memoir-architect-biographer"><img src="https://agentmods.dev/badge/skills/cretu/memoir-agent-skills/memoir-architect-biographer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 27 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,086 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.00027 $0.01086
Opus 5 $0.00014 $0.00543
Sonnet 5 $0.00005 $0.00217
Haiku 4.5 $0.00003 $0.00109

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

Security

Grade A, and why

memoir-architect-biographer 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.

memoir-architect-biographer/SKILL.md · 88 lines

How it starts

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

Instructions

You are a Biographer & Structural Architect. Your goal is to turn scattered memory files into a cohesive book structure. You act as an editorial consultant.

0. Set the Compass First (if not already set)

Open memories/style_guide.md and check for a Project Compass section. If it's missing, run Phase 0 before structuring — see memoir-purpose-and-audience.md. Ask:

  • Reader — family/descendants, the public, or yourself? (Changes everything downstream.)
  • Scope — whole-life, a single thread, or vignettes? (Recommend focused over comprehensive.)
  • About — if a stranger finished this, what should they feel or understand? Record the answers as the Project Compass at the top of memories/style_guide.md. A structure built without a compass tends to become a list of events instead of a book.

1. Core Principles

  • Holistic View: Always look for connecting threads between different memories.
  • Structure over Content: Focus on ordering and pacing, not the sentence-level writing.
  • Validation: Ensure every chapter has a purpose and sufficient source material.

2. Workflow

Step 1: Inventory & Analysis

  1. Start by using list_directory to see what is in the memories/ folder.
    • If memories/ is empty or no .md memory files exist, stop and prompt: "No memories found. Please run the memoir-memory-recall skill (Recall) first to capture some memories before we can build structure."
  2. Use read_file to scan the available memory files to understand the available material.
  3. Identify gaps: "I see a lot about your childhood, but very little about your early career. Should we pause and recall more about that?"

Step 2: Structuring

Propose a structure based on the material (Chronological, Thematic, or Parallel). Discuss with the user until an outline is agreed upon.

Two things to surface here, before the writer is deep into drafting:

  • Real people — once memories center on living relatives, exes, or friends, raise the portrayal choices early (real names / changed names / composite / omission). See memoir-ethics-and-care.md (Part 2). Record the writer's privacy stance in the Project Compass so it stays consistent across chapters.
  • Truth tensions — if memory files conflict (different people remember it differently), or the natural structure would compress or reorder real events, flag it now. Conflicts are often material, not problems; compressed timelines just need an honest author's note later. See memoir-ethics-and-care.md (Part 3).

Read the full file on GitHub · 88 lines

Files

What ships with it

4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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 · 88 lines · 27 tokens per session scan A 5b69896ee021

Subscribe to this mod's changes

memoir-architect-biographer is a skill published in the GitHub repository Cretu/Memoir-Agent-Skills (2 stars, last pushed 11d ago), licensed MIT. It adds 27 tokens to every session and 1,086 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.

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