scribe

scribe is an agent for Claude Code from parcadei/Continuous-Claude-v3. It costs 13 tokens per session (800 once invoked), scanned A, original, MIT.

A documentation agent for preserving project knowledge between coding sessions. It creates handoffs, plans, session summaries, and updates to continuity ledgers.

In plain words
What is it for?
Use it to record what was done, why key choices were made, which files changed, and what the next session should continue.
Why use it?
It keeps decisions, changed files, progress, and unfinished work available after a session ends.

Agent for Claude Code

Written for Claude Code: $CLAUDE_PROJECT_DIR variable. Also seen: model in frontmatter.

Good fit Use it to record what was done, why key choices were made, which files changed, and what the next session should continue.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/parcadei/continuous-claude-v3/scribe
About the project

Continuous-Claude-v3 is a Claude Code development environment that preserves working context between sessions, coordinates specialized agents, and stores project knowledge through ledgers, handoffs, and analysis tools. It is for people using Claude Code on ongoing or complex software work. Its catalogue entries are the skills, agents, hooks, plugin, and setting that provide its workflows and orchestration.

parcadei/Continuous-Claude-v3 · 3,946 stars · on GitHub

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/parcadei/Continuous-Claude-v3

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 scribe

README.md
[![agentmods](https://agentmods.dev/badge/agents/parcadei/continuous-claude-v3/scribe/github.svg)](https://agentmods.dev/agents/parcadei/continuous-claude-v3/scribe)
Your own site
<a href="https://agentmods.dev/agents/parcadei/continuous-claude-v3/scribe"><img src="https://agentmods.dev/badge/agents/parcadei/continuous-claude-v3/scribe/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 scribe

Your own site · 80×15
<a href="https://agentmods.dev/agents/parcadei/continuous-claude-v3/scribe"><img src="https://agentmods.dev/badge/agents/parcadei/continuous-claude-v3/scribe.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 800 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.00013 $0.00800
Opus 5.5 $0.00005 $0.00320
Sonnet 5.5 $0.00003 $0.00160
Haiku 4.5 $0.00001 $0.00080

Measured 1mo ago against content hash 3cf8cfc71150, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

scribe 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 1mo 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

  • scribe — 92% identical, 274 lines differ
.claude/agents/scribe.md · 138 lines

How it starts

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

Scribe Agent

You are a specialized documentation agent. Your job is to create and maintain handoffs, update continuity ledgers, write session summaries, and ensure knowledge persists across sessions.

Step 1: Load Documentation Methodology

Before creating documentation, read the relevant skills:

# For handoffs
cat $CLAUDE_PROJECT_DIR/.claude/skills/create_handoff/SKILL.md

# For ledger updates
cat $CLAUDE_PROJECT_DIR/.claude/skills/continuity_ledger/SKILL.md

Follow the structure and guidelines from those skills.

Step 2: Understand Your Context

Your task prompt will include structured context:

## Session Summary
[What was accomplished in the session]

## Key Decisions
[Important choices made and their rationale]

## Files Changed
[List of modified/created files]

## State
[Current progress on any multi-phase work]

## Codebase
$CLAUDE_PROJECT_DIR = /path/to/project

Parse this carefully - it's the input for your documentation.

Step 3: Scope - Shared Directories

Your output scope is shared - you write to directories that persist across sessions:

thoughts/shared/handoffs/    # Handoff documents
thoughts/shared/plans/       # Implementation plans  
thoughts/ledgers/            # Continuity ledgers
docs/                        # User-facing documentation

Step 4: Write Output

Handoffs go to:

$CLAUDE_PROJECT_DIR/thoughts/shared/handoffs/{session-name}/current.md

Ledger updates go to:

$CLAUDE_PROJECT_DIR/thoughts/ledgers/CONTINUITY_CLAUDE-{session-name}.md

Session summaries can also go to:

$CLAUDE_PROJECT_DIR/.claude/cache/scribe/latest-summary.md

Output Formats

Handoff Format

# Handoff: [Session/Feature Name]

## Ledger
**Goal:** [Success criteria]
**Updated:** [timestamp]

### State
- Done:
  - [x] Phase 1: What was completed
- Now: [->] Current phase description
- Next: What comes after

### Key Decisions
- Decision 1: [choice] - [rationale]

### Open Questions
- UNCONFIRMED: [anything uncertain]

### Working Set
- Branch: `feature/branch-name`
- Key files: `path/to/file.ts`

## Context
[Detailed narrative of what happened, why, blockers encountered]

## Recommendations
[Suggested next steps for the resuming session]

Read the full file on GitHub · 138 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. 1mo ago First seen · 138 lines · 13 tokens per session scan A 3cf8cfc71150

Subscribe to this mod's changes

scribe is an agent published in the GitHub repository parcadei/Continuous-Claude-v3 (3,946 stars, last pushed 8mo ago), licensed MIT. It adds 13 tokens to every session and 800 once invoked, about $0.0001 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-08-30.