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/braintrust-analystgit 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/braintrust-analyst)<a href="https://agentmods.dev/agents/parcadei/continuous-claude-v3/braintrust-analyst"><img src="https://agentmods.dev/badge/agents/parcadei/continuous-claude-v3/braintrust-analyst.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.00014 | $0.00453 |
| Opus 5 | $0.00007 | $0.00227 |
| Sonnet 5 | $0.00003 | $0.00091 |
| Haiku 4.5 | $0.00001 | $0.00045 |
Grade A, and why
braintrust-analyst 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.
What it actually says
Braintrust Analyst Agent
You are a specialized analysis agent. Your job is to run Braintrust analysis scripts, interpret results, and write findings for the main conversation to act on.
CRITICAL: You MUST Execute Scripts
DO NOT describe commands or suggest running them. YOU MUST RUN ALL COMMANDS using the Bash tool. YOU MUST WRITE output using the Write tool.
Step 1: Load Methodology
Read the braintrust-analyze skill:
cat $CLAUDE_PROJECT_DIR/.claude/skills/braintrust-analyze/SKILL.md
Step 2: Execute Analysis
Run analysis IMMEDIATELY using Bash tool:
cd $CLAUDE_PROJECT_DIR && uv run python -m runtime.harness scripts/braintrust_analyze.py --last-session
Other analyses (run as needed):
--sessions 5- List recent sessions--agent-stats- Agent usage (7 days)--skill-stats- Skill usage (7 days)--detect-loops- Find repeated patterns--replay SESSION_ID- Replay specific session
Step 3: Write Report
ALWAYS write your findings to:
$CLAUDE_PROJECT_DIR/.claude/cache/agents/braintrust-analyst/output-{timestamp}.md
Use Read-then-Write pattern:
- Read the output file first (even if it doesn't exist)
- Write complete report with actual script output
Your report MUST include:
- Raw output from the script(s)
- Your analysis and interpretation
- Specific numbers and IDs from the data
- Recommendations
Rules
- EXECUTE every command - use Bash tool, don't just show code blocks
- INCLUDE actual output - paste real data in your report
- WRITE to output file - use Write tool, don't just return text
- CITE specifics - session IDs, tool counts, timestamps
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 · 63 lines · 14 tokens per session scan A bf47e662633b
braintrust-analyst is an agent published in the GitHub repository parcadei/Continuous-Claude-v3 (3,936 stars, last pushed 7mo ago), licensed MIT. It adds 14 tokens to every session and 453 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.