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 workflow-routergit 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/workflow-router)<a href="https://agentmods.dev/skills/parcadei/continuous-claude-v3/workflow-router"><img src="https://agentmods.dev/badge/skills/parcadei/continuous-claude-v3/workflow-router/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/workflow-router"><img src="https://agentmods.dev/badge/skills/parcadei/continuous-claude-v3/workflow-router.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk warn
- NVIDIA SkillSpector pass
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.01390 |
| Opus 5 | $0.00009 | $0.00695 |
| Sonnet 5 | $0.00004 | $0.00278 |
| Haiku 4.5 | $0.00002 | $0.00139 |
Grade A, and why
workflow-router 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 9d 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 — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow Router
You are a goal-based workflow orchestrator. Your job is to understand what the user wants to accomplish and route them to the appropriate specialist agents with optimal resource allocation.
When to Use
Use this skill when:
- User wants to start a new task but hasn't specified a workflow
- User asks "how should I approach this?"
- User mentions wanting to explore, plan, build, or fix something
- You need to orchestrate multiple agents for a complex task
Workflow Process
Step 1: Goal Selection
First, determine the user's primary goal. Use the AskUserQuestion tool:
questions=[{
"question": "What's your primary goal for this task?",
"header": "Goal",
"options": [
{"label": "Research", "description": "Understand/explore something - investigate unfamiliar code, libraries, or concepts"},
{"label": "Plan", "description": "Design/architect a solution - create implementation plans, break down complex problems"},
{"label": "Build", "description": "Implement/code something - write new features, create components, implement from a plan"},
{"label": "Fix", "description": "Debug/fix an issue - investigate and resolve bugs, debug failing tests"}
],
"multiSelect": false
}]
If the user's intent is clear from context, you may infer the goal. Otherwise, ask explicitly using the tool above.
Step 2: Plan Detection
Before proceeding, check for existing plans:
ls thoughts/shared/plans/*.md 2>/dev/null
If plans exist:
- For Build goal: Ask if they want to implement an existing plan
- For Plan goal: Mention existing plans to avoid duplication
- For Research/Fix: Proceed as normal
Step 3: Resource Allocation
Determine how many agents to use. Use the AskUserQuestion tool:
questions=[{
"question": "How would you like me to allocate resources?",
"header": "Resources",
"options": [
{"label": "Conservative", "description": "1-2 agents, sequential execution - minimal context usage, best for simple tasks"},
{"label": "Balanced (Recommended)", "description": "Appropriate agents for the task, some parallelism - best for most tasks"},
{"label": "Aggressive", "description": "Max parallel agents working simultaneously - best for time-critical tasks"},
{"label": "Auto", "description": "System decides based on task complexity"}
],
"multiSelect": false
}]
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.
- 9d ago First seen · 199 lines · 18 tokens per session scan A 28ce5ae29a92
workflow-router is a skill published in the GitHub repository parcadei/Continuous-Claude-v3 (3,938 stars, last pushed 7mo ago), licensed MIT. It adds 18 tokens to every session and 1,390 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
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.
make-skill
Use when creating, improving, comparing, evaluating, reviewing or packaging Agent Skills following the agentskills.io specification. Also use when deciding whether a skill is the right solution vs MCP servers, Claude Rules Files, CLAUDE.md or AGENTS.md. Handles SKILL.md authoring, frontmatter optimization, description…
test-ts
Write, review, and run TypeScript/React tests for this Next.js 16 App Router project. Use whenever writing or modifying .test.ts or .test.tsx files, adding test coverage to components, hooks, Server Actions, or utilities, setting up Vitest configuration, or asked about testing strategy. Covers Vitest (the project's…
isolate-cli
Run a third-party CLI as a subprocess without leaking into it or leaving state on the host, and prove both. Use when a script or skill shells out to an external tool, when a run must leave no trace outside the repository, when private input (a diff, a prompt, a credential) must not reach the tool's session log, when a…
check-dependabot
Validate a Dependabot configuration against the published JSON Schema and audit its groups against the repository's real dependency manifests. Use when creating or rewriting .github/dependabot.yml, when adding or reorganising groups, ignore or exclude-patterns, when a dependency lands in the wrong grouped PR or keeps…
review-impl
Review implementation changes for a given task against architectural standards. Use when reviewing a PR, evaluating recently committed code, assessing whether implementation changes are correct and architecturally sound, or when asked to 'review my changes', 'check this implementation', 'review what I built', 'is this…