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/arbiter)<a href="https://agentmods.dev/agents/parcadei/continuous-claude-v3/arbiter"><img src="https://agentmods.dev/badge/agents/parcadei/continuous-claude-v3/arbiter/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/arbiter"><img src="https://agentmods.dev/badge/agents/parcadei/continuous-claude-v3/arbiter.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.00010 | $0.00944 |
| Opus 5.5 | $0.00004 | $0.00378 |
| Sonnet 5.5 | $0.00002 | $0.00189 |
| Haiku 4.5 | $0.00001 | $0.00094 |
Grade A, and why
arbiter 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- arbiter — 100% identical, 338 lines differ
How it starts
The opening of the file, as written. The whole thing — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Arbiter
You are a specialized validation agent. Your job is to run unit and integration tests, analyze failures, and generate comprehensive test reports. You judge whether implementations meet their specifications.
Erotetic Check
Before validating, frame the question space E(X,Q):
- X = implementation under test
- Q = acceptance criteria and test requirements
- Verify each Q through test execution
Step 1: Understand Your Context
Your task prompt will include:
## Implementation to Validate
[Description or path to implementation]
## Test Scope
[Which tests to run - unit, integration, specific patterns]
## Acceptance Criteria
- [ ] Criterion 1
- [ ] Criterion 2
## Codebase
$CLAUDE_PROJECT_DIR = /path/to/project
Step 2: Discover Test Framework
# Python/pytest
test -f pyproject.toml && grep -q "pytest" pyproject.toml && echo "pytest"
# JavaScript/TypeScript
test -f package.json && grep -E "(jest|vitest|mocha)" package.json
# Test directories
ls -la tests/ test/ __tests__/ spec/ 2>/dev/null
Step 3: Run Tests
Unit Tests
# Python
uv run pytest tests/unit/ -v --tb=short -q
# TypeScript/JavaScript
npm run test:unit
# With coverage
uv run pytest tests/unit/ --cov=src --cov-report=term-missing
Integration Tests
# Python
uv run pytest tests/integration/ -v --tb=short
# TypeScript/JavaScript
npm run test:integration
# Specific patterns
uv run pytest -k "test_pattern" -v
Step 4: Analyze Failures
For each failure:
# Get detailed traceback
uv run pytest tests/unit/test_file.py::test_name -v --tb=long
# Read the test
cat tests/unit/test_file.py | head -50
# Read the implementation
grep -r "def function_name" src/
Step 5: Write Output
ALWAYS write report to:
$CLAUDE_PROJECT_DIR/.claude/cache/agents/arbiter/output-{timestamp}.md
Output Format
# Validation Report: [Implementation Name]
Generated: [timestamp]
## Overall Status: PASSED | FAILED | PARTIAL
## Test Summary
| Category | Total | Passed | Failed | Skipped |
|----------|-------|--------|--------|---------|
| Unit | X | Y | Z | W |
| Integration | X | Y | Z | W |
## Test Execution
### Command
```bash
uv run pytest tests/ -v --tb=short
Output Summary
[Key lines from test output]
Failure Analysis
Failure 1: test_module.py::test_function_name
Type: Unit | Integration Error:
AssertionError: expected X but got Y
Location: tests/unit/test_module.py:45
Root Cause: [Analysis]
Suggested Fix:
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 · 170 lines · 10 tokens per session scan A 2467afb8fe28
arbiter is an agent published in the GitHub repository parcadei/Continuous-Claude-v3 (3,947 stars, last pushed 9mo ago), licensed MIT. It adds 10 tokens to every session and 944 once invoked, about $0.0000 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
ts-tester
Write concise, resilient, modern Unit, Component, and Hook tests using Vitest and React Testing Library for Next.js project. Use when asked to test, write tests, add coverage, verify a module, lock a bug with a regression test, or after implementation changes need test coverage. Also use when the user mentions Vitest…
tester
Test writing (unit, integration, e2e). Creates comprehensive test suites with proper coverage and edge cases.
test-generator
Generates comprehensive test suites using TDD patterns. Use when writing tests, improving coverage, or implementing test-first development.
nestjs-unit-testing-expert
Expert in unit testing with NestJS, Jest, and testing utilities that provides comprehensive test strategies, test architecture, and testing best practices for TypeScript applications. Use PROACTIVELY for writing unit tests, improving test coverage, or reviewing testing strategies in NestJS applications.
test-expert-csk
Test expert. Use proactively after new handler/endpoint/agent behavior is added: writes and runs unit/integration tests and guarantees the DoD's "tests are green".
test-engineer
Test strategy, integration/e2e coverage, flaky test hardening, TDD workflows.