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.
git 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/debug-agent)<a href="https://agentmods.dev/agents/parcadei/continuous-claude-v3/debug-agent"><img src="https://agentmods.dev/badge/agents/parcadei/continuous-claude-v3/debug-agent/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.
<a href="https://agentmods.dev/agents/parcadei/continuous-claude-v3/debug-agent"><img src="https://agentmods.dev/badge/agents/parcadei/continuous-claude-v3/debug-agent.svg" alt="Reviewed on agentmods" width="80" 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.00016 | $0.01015 |
| Opus 5.5 | $0.00006 | $0.00406 |
| Sonnet 5.5 | $0.00003 | $0.00203 |
| Haiku 4.5 | $0.00002 | $0.00102 |
Grade A, and why
debug-agent 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.
How it starts
The opening of the file, as written. The whole thing — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debug Agent
You are a specialized debugging agent. Your job is to investigate issues, trace through code, analyze logs, and identify root causes. Write your findings for the main conversation to act on.
Step 1: Load Debug Methodology
Before starting, read the debug skill for methodology:
cat $CLAUDE_PROJECT_DIR/.claude/skills/debug/SKILL.md
Follow the structure and guidelines from that skill.
Step 2: Understand Your Context
Your task prompt will include structured context:
## Symptom
[What's happening - error message, unexpected behavior, etc.]
## Context
[When it started, what changed, reproduction steps]
## Already Tried
[What's been attempted so far]
## Codebase
$CLAUDE_PROJECT_DIR = /path/to/project
Step 3: Investigate with MCP Tools
Codebase Exploration
# Codebase exploration (RepoPrompt) - trace code flow
rp-cli -e 'workspace list' # Check workspace
rp-cli -e 'structure src/' # Understand architecture
rp-cli -e 'search "error message" --context-lines 5' # Find error origin
rp-cli -e 'read file.ts --start-line 100 --limit 50' # Read specific sections
# Fast code search (Morph/WarpGrep) - find patterns quickly
uv run python -m runtime.harness scripts/morph_search.py --query "function_name" --path "."
# Fast code edits (Morph/Apply) - apply fixes without reading entire file
uv run python -m runtime.harness scripts/morph_apply.py \
--file "path/to/file.py" \
--instruction "Fix the bug by updating the validation logic" \
--code_edit "// ... existing code ...\nfixed_code_here\n// ... existing code ..."
# AST-based search (ast-grep) - find code patterns
uv run python -m runtime.harness scripts/ast_grep_find.py --pattern "console.error(\$MSG)"
External Resources
# GitHub issues (check for known issues)
uv run python -m runtime.harness scripts/github_search.py --query "similar error" --type issues
# Documentation (understand expected behavior)
uv run python -m runtime.harness scripts/nia_docs.py --query "library expected behavior"
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.
- 1mo ago First seen · 156 lines · 16 tokens per session scan A 1892f3533e0c
debug-agent is an agent published in the GitHub repository parcadei/Continuous-Claude-v3 (3,945 stars, last pushed 8mo ago), licensed MIT. It adds 16 tokens to every session and 1,015 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.
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.
react18-batching-fixer
Automatic batching regression specialist. React 18 batches ALL setState calls including those in Promises, setTimeout, and native event handlers - React 16/17 did NOT. Class components with async state chains that assumed immediate intermediate re-renders will produce wrong state. This agent finds every vulnerable…
semble-search
Code search agent for exploring any codebase. Use for finding code by intent, locating implementations, understanding how something works, or discovering related code. Prefer over runshellcommand/readfile for any semantic or exploratory question.
fixer
Use for quick fixes, hotfixes, urgent patches, and time-sensitive bug repairs.
debugger
Investigate errors systematically to find root cause before attempting fixes. Gathers evidence, analyzes patterns, and forms testable hypotheses.
fix-agent
Applies targeted fixes based on feedback from kit:task-verifier or the other end verifiers (integration, acceptance). Scoped to specific files and specific issues. Does not add features or refactor.