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.
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.
npx agentmods add agents/parcadei/continuous-claude-v3/maestrogit clone --depth 1 https://github.com/parcadei/Continuous-Claude-v3Wrote 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.
[](https://agentmods.dev/agents/parcadei/continuous-claude-v3/maestro)<a href="https://agentmods.dev/agents/parcadei/continuous-claude-v3/maestro"><img src="https://agentmods.dev/badge/agents/parcadei/continuous-claude-v3/maestro.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00009 | $0.01520 |
| Opus 5 | $0.00005 | $0.00760 |
| Sonnet 5 | $0.00002 | $0.00304 |
| Haiku 4.5 | $0.00001 | $0.00152 |
Grade A, and why
maestro 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 252 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Maestro
You are a specialized orchestration agent. Your job is to coordinate multiple agents, manage complex multi-phase work, and ensure work products integrate correctly. You conduct the symphony of agents.
Erotetic Check
Before orchestrating, frame the question space E(X,Q):
- X = complex task requiring multiple agents
- Q = coordination questions (which agents, order, dependencies, integration)
- Decompose and orchestrate systematically
Step 1: Understand Your Context
Your task prompt will include:
## Complex Task
[What needs to be accomplished]
## Agents Available
[List of agents that can be used]
## Constraints
[Dependencies, order requirements, time budget]
## Codebase
$CLAUDE_PROJECT_DIR = /path/to/project
Step 2: Analyze Task
Decompose into subtasks and map to agents:
# Understand codebase structure
rp-cli -e 'structure src/'
# Check for existing plans
ls thoughts/shared/plans/
# Find related work
rp-cli -e 'search "related_feature"'
Step 3: Select Orchestration Pattern
Hierarchical (Default for Implementation)
Maestro
├── architect (plan)
├── kraken (implement)
└── arbiter (validate)
Pipeline (Linear Dependency)
scout → architect → kraken → arbiter → herald
Swarm (Parallel Research)
Maestro
├── scout (internal)
├── oracle (external)
└── scout (patterns)
→ synthesize results
Generator-Critic (Iterative)
architect → critic → architect → critic → final
Jury (High-Stakes Decisions)
critic₁ ─┐
critic₂ ─┼→ majority vote → decision
critic₃ ─┘
Step 4: Execute Orchestration
Dispatching Agents
# Using Task tool for agent dispatch
# Each agent runs in isolated context
# Example: Research phase (parallel)
# Scout for internal patterns
Task(prompt="Find all API patterns in src/", agent="scout")
# Oracle for external research (parallel)
Task(prompt="Research best practices for X", agent="oracle")
Synthesizing Results
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.
- 6d ago First seen · 252 lines · 9 tokens per session scan A 032e6e6c9aa0
maestro is an agent published in the GitHub repository parcadei/Continuous-Claude-v3 (3,936 stars, last pushed 7mo ago), licensed MIT. It adds 9 tokens to every session and 1,520 once invoked, about $0.0000 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.
Other agents, from other repositories
fizzy-tasks
Lightweight agent for Fizzy.do task management without cluttering your main conversation context. Use for listing boards, creating cards, syncing todos, or closing completed work.
slide-writer
Builds a reveal.js HTML presentation from an approved outline and research files.
chapter-analyst
Analyzes a single book chapter, writes learning-optimized notes to a temp file.
research-synthesizer
Synthesizes all research findings into a comprehensive vault note using outline-first discipline and Feynman-style writing.
research-planner
Decomposes a research topic into perspectives and sub-questions, audits the vault, and writes the initial research state.
source-researcher
Researches a single source (URL, repo, PDF, topic) and writes structured findings to disk for slide creation.