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 skills add parcadei/Continuous-Claude-v3 --skill helpgit 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/help)<a href="https://agentmods.dev/skills/parcadei/continuous-claude-v3/help"><img src="https://agentmods.dev/badge/skills/parcadei/continuous-claude-v3/help/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/skills/parcadei/continuous-claude-v3/help"><img src="https://agentmods.dev/badge/skills/parcadei/continuous-claude-v3/help.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk warn
- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 281 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 282 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.02380 |
| Opus 5 | $0.00009 | $0.01190 |
| Sonnet 5 | $0.00004 | $0.00476 |
| Haiku 4.5 | $0.00002 | $0.00238 |
Grade A, and why
help 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.
How it starts
The opening of the file, as written. The whole thing — 364 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/help - Workspace Discovery
Guide users through the capabilities of this workspace setup.
Usage
/help # Interactive guided discovery
/help workflows # Workflow orchestration skills
/help agents # Specialist agents catalog
/help tools # CLI tools (tldr, prove, recall)
/help hooks # Active hooks and what they do
/help advanced # MCP, frontmatter, customization
/help <name> # Deep dive on specific skill/agent
Behavior Based on Arguments
No Arguments: Interactive Discovery
Use AskUserQuestion to guide the user:
question: "What are you trying to do?"
header: "Goal"
options:
- label: "Explore/understand a codebase"
description: "Find patterns, architecture, conventions"
- label: "Fix a bug"
description: "Investigate, diagnose, implement fix"
- label: "Build a feature"
description: "Plan, implement, test new functionality"
- label: "Prove something mathematically"
description: "Formal verification with Lean 4"
Based on response, show relevant tools:
| Goal | Show |
|---|---|
| Explore codebase | scout agent, tldr CLI, /explore workflow |
| Fix a bug | /fix workflow, sleuth agent, debug-agent |
| Build feature | /build workflow, architect agent, kraken agent |
| Prove math | /prove skill, lean4 skill, Godel-Prover |
| Research docs | oracle agent, nia-docs, perplexity |
| Configure workspace | hooks, rules, settings, frontmatter |
/help workflows
Display workflow meta-skills:
## Workflow Skills
Orchestrate multi-agent pipelines for complex tasks.
| Workflow | Purpose | Agents Used |
|----------|---------|-------------|
| /fix | Bug investigation → diagnosis → implementation | sleuth → kraken → arbiter |
| /build | Feature planning → implementation → testing | architect → kraken → arbiter |
| /debug | Deep investigation of issues | debug-agent, sleuth |
| /tdd | Test-driven development cycle | arbiter → kraken → arbiter |
| /refactor | Code transformation with safety | phoenix → kraken → judge |
| /review | Code review and feedback | critic, judge |
| /security | Vulnerability analysis | aegis |
| /explore | Codebase discovery | scout |
| /test | Test execution and validation | arbiter, atlas |
| /release | Version bumps, changelog | herald |
| /migrate | Framework/infrastructure changes | pioneer, phoenix |
**Usage**: Just describe your goal. Claude routes to the right workflow.
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 · 364 lines · 18 tokens per session scan A 3ae90de0d374
help is a skill 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 2,380 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-09-03.
Other skills, from other repositories
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.
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…
sfl
Save For Later: checkpoint this window so a fresh session (or /nil) can resume it later. Use when the user types /sfl, "save for later", or "checkpoint this window". Writes a live per-window entry under /.claude/sfl/ (plus an optional durable note in the user's own memory system), then shows the green Saved-for-Later…
headsup-colors
Customize headsup's global iTerm2 tab colors for Codex sessions: idle, working, and waiting. Use when the user asks to change Codex/headsup tab colors.
headsup-notifications
Manage macOS notifications for Codex tabs that have been waiting longer than a configured threshold.
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.