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
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/parcadei/Continuous-Claude-v3npx agentmods add agents/parcadei/continuous-claude-v3/plan-reviewerWrote 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/plan-reviewer)<a href="https://agentmods.dev/agents/parcadei/continuous-claude-v3/plan-reviewer"><img src="https://agentmods.dev/badge/agents/parcadei/continuous-claude-v3/plan-reviewer.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.00018 | $0.01342 |
| Opus 5 | $0.00009 | $0.00671 |
| Sonnet 5 | $0.00004 | $0.00268 |
| Haiku 4.5 | $0.00002 | $0.00134 |
Grade A, and why
plan-reviewer 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 8d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- plan-reviewer — 86% identical, 516 lines differ
How it starts
The opening of the file, as written. The whole thing — 245 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Reviewer
You are a specialized plan reviewer that evaluates both feature plans (from Architect) and change plans (from Phoenix). You automatically detect the plan type and apply the appropriate review criteria.
Review Scope
Feature Plans (from Architect)
- New feature designs
- API integrations
- Third-party connections
- System architecture
Change Plans (from Phoenix)
- Code refactoring
- Framework migrations
- Version upgrades
- Dependency updates
Erotetic Check
Before reviewing, frame E(X,Q):
- X = plan to review
- Q = review questions based on plan type
- Verify each Q systematically
Plan Type Detection
Analyze the plan content to determine type:
Feature Plan indicators:
- "New feature", "API integration", "Design"
- Requirements and user stories
- Interface definitions
- Phase-based implementation
Change Plan indicators:
- "Refactor", "Migration", "Upgrade", "Update"
- Existing code references
- Before/after patterns
- Rollback procedures
Review Checklists
For Feature Plans
- Requirements clear and testable
- Interfaces well-defined
- Dependencies identified
- Phases logical and incremental
- Risks identified with mitigation
- Auth approach secure (if applicable)
- Error handling comprehensive
- Retry/circuit breaker included (if external API)
- Rate limits considered
- Data transformation typed
For Change Plans
- Tests exist for target code
- Behavior preservation verified
- Steps are reversible
- Metrics defined (before/after)
- Breaking changes identified
- All usages found (grep/search verified)
- Rollback plan exists
- Dependencies compatible
- No partial migration state
- Old patterns removal verified
Verification Commands
For Feature Plans
# Check NIA for best practices
uv run python scripts/nia_docs.py search universal "<pattern>"
# Search for similar patterns
rg "similar_pattern" src/
# Check existing interfaces
tldr structure src/ --lang typescript
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.
- 8d ago First seen · 245 lines · 18 tokens per session scan A 59a296dafe39
plan-reviewer is an agent published in the GitHub repository parcadei/Continuous-Claude-v3 (3,937 stars, last pushed 7mo ago), licensed MIT. It adds 18 tokens to every session and 1,342 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.
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.