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 skills/parcadei/continuous-claude-v3/trace-claude-codenpx skills add parcadei/Continuous-Claude-v3 --skill trace-claude-codegit 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/skills/parcadei/continuous-claude-v3/trace-claude-code)<a href="https://agentmods.dev/skills/parcadei/continuous-claude-v3/trace-claude-code"><img src="https://agentmods.dev/badge/skills/parcadei/continuous-claude-v3/trace-claude-code.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.00032 | $0.01565 |
| Opus 5 | $0.00016 | $0.00783 |
| Sonnet 5 | $0.00006 | $0.00313 |
| Haiku 4.5 | $0.00003 | $0.00156 |
Grade C, and why
trace-claude-code scanned grade C with 2 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- **Ubuntu/Debian**: `sudo apt-get install jq` Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
tail -f ~/.claude/state/braintrust_hook.log How it starts
The opening of the file, as written. The whole thing — 248 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Trace Claude Code to Braintrust
Automatically send Claude Code conversations to Braintrust for tracing and observability. Get full visibility into your AI coding sessions with hierarchical traces showing sessions, turns, and every tool call.
What you get
Claude Code Session (root trace)
├── Turn 1: "Add error handling"
│ ├── Read: src/app.ts
│ ├── Edit: src/app.ts
│ └── Response: "I've added try-catch..."
├── Turn 2: "Now run the tests"
│ ├── Terminal: npm test
│ └── Response: "All tests pass..."
└── Turn 3: "Great, commit this"
├── Terminal: git add .
├── Terminal: git commit -m "..."
└── Response: "Changes committed..."
How it works
Four hooks capture the complete workflow:
| Hook | What it captures |
|---|---|
| SessionStart | Creates root trace when you start Claude Code |
| PostToolUse | Captures every tool call (file reads, edits, terminal commands) |
| Stop | Captures conversation turns (your message + Claude's response) |
| SessionEnd | Logs session summary when you exit |
Quick setup
Run the setup script in any project directory where you want tracing:
bash /path/to/skills/trace-claude-code/setup.sh
The script prompts for your API key and project name, then configures all hooks automatically.
Manual setup
Prerequisites
- Claude Code CLI installed
- Braintrust API key
jqcommand-line tool (brew install jqon macOS)
Configuration
Create .claude/settings.local.json in your project directory:
{
"hooks": {
"SessionStart": [
{
"hooks": [
{
"type": "command",
"command": "bash /path/to/hooks/session_start.sh"
}
]
}
],
"PostToolUse": [
{
"matcher": "*",
"hooks": [
{
"type": "command",
"command": "bash /path/to/hooks/post_tool_use.sh"
}
]
}
],
"Stop": [
{
"hooks": [
{
"type": "command",
"command": "bash /path/to/hooks/stop_hook.sh"
}
]
}
],
"SessionEnd": [
{
"hooks": [
{
"type": "command",
"command": "bash /path/to/hooks/session_end.sh"
}
]
}
]
},
"env": {
"TRACE_TO_BRAINTRUST": "true",
"BRAINTRUST_API_KEY": "sk-...",
"BRAINTRUST_CC_PROJECT": "my-project"
}
}
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 · 248 lines · 32 tokens per session scan C b0ad931e0f58
trace-claude-code is a skill published in the GitHub repository parcadei/Continuous-Claude-v3 (3,936 stars, last pushed 7mo ago), licensed MIT. It adds 32 tokens to every session and 1,565 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 2 findings (asks for root, reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
fizzy-workflow
Use for guided Fizzy.do workflows: "set up Fizzy", "configure Fizzy for this project", "sync my work to Fizzy", "review my Fizzy progress", "end of session cleanup". Provides step-by-step guidance for common operations.
tdd
Use when implementing features or bug fixes test-first.
nil
The inverse of /sfl. Where sfl saved each window for later, /nil says later is now: it reopens them. You choose which to bring back.
e2e-test-skill
E2E test skill for validation.
headsup-config
Unified settings hub for headsup (Claude Code's iTerm2 status hooks). One command with a section as the first word, then that section's args. Sections: newtabs (New Claude Tab / Cmd-Opt-C launch mode), colors (idle/processing/waiting tab colors), label (this tab's title + badge), notify (the 'Claude is waiting' macOS…
headsup-label
Set or clear the current Codex window label in AI Power Term or iTerm2. Use when the user wants a custom Codex tab title, badge, or watermark.