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
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/tdd-migrate)<a href="https://agentmods.dev/skills/parcadei/continuous-claude-v3/tdd-migrate"><img src="https://agentmods.dev/badge/skills/parcadei/continuous-claude-v3/tdd-migrate/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/tdd-migrate"><img src="https://agentmods.dev/badge/skills/parcadei/continuous-claude-v3/tdd-migrate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk 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.00019 | $0.01528 |
| Opus 5 | $0.00010 | $0.00764 |
| Sonnet 5 | $0.00004 | $0.00306 |
| Haiku 4.5 | $0.00002 | $0.00153 |
Grade A, and why
tdd-migrate 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 5d 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 — 255 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TDD Migrate
Orchestrate TDD migrations with agents doing all work. Main context stays clean.
When to Use
- "Port X from Python to TypeScript"
- "Create N adapters following existing pattern"
- "Migrate module to new architecture"
- "TDD implementation of multiple similar items"
Parameters
/tdd-migrate <source_path> <target_path> --pattern <reference> --items "item1,item2,item3"
source_path: Path to analyze (existing code)target_path: Where to create new codepattern: Reference file/pattern to followitems: Comma-separated list of things to create
Workflow
Phase 0: YAML TODO List
│
▼
Phase 1: TLDR Analysis ─────────────────┐
│ │
▼ │ Parallel scouts
Phase 2: Write Failing Tests ───────────┤ per item
│ │
▼ │
Phase 3: Implement (minimal) ───────────┤
│ │
▼ │
Phase 4: Build + Pass Tests ────────────┘
│
▼
Phase 5: QLTY Check ────────────────────┐
│ │ Parallel
Phase 6: Review Agent Validates ────────┘
│
▼
Phase 7: TLDR Diff (new vs reference)
│
▼
Phase 8: Fix Issues (if any)
│
▼
Complete
Key Principles
-
Main context = orchestration only
- Never read files directly (use scout)
- Never implement directly (use kraken/spark)
- Never run tests directly (use validator)
- Only pipe context and coordinate
-
Agents do ALL work
Task Agent Explore/analyze scout Write tests + implement kraken Quick fixes spark Run tests/validate validator Code review critic -
Parallel where independent
- All items can be implemented in parallel if independent
- Review + QLTY run in parallel
- TLDR analysis runs in parallel with planning
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.
- 5d ago First seen · 255 lines · 19 tokens per session scan A 21ef4e9de16f
tdd-migrate is a skill published in the GitHub repository parcadei/Continuous-Claude-v3 (3,936 stars, last pushed 7mo ago), licensed MIT. It adds 19 tokens to every session and 1,528 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
tdd
Use when implementing features or bug fixes test-first.
writing-skills
Use when creating a new forge-skill, editing an existing skill, when planning to contribute to forge-skills, when a session has produced a one-off prompt that should be promoted to a skill, or when verifying a skill works before deployment.
tdd
Use when implementing features or fixing bugs test-first, when user mentions "red-green-refactor", when test discipline is required for a specific task, when incremental-implementation needs TDD enforcement, or when a behavior change needs a failing test before any code is written.
incremental-implementation
Use when .forge/tasks.yaml exists and implementation is starting, when executing a planned task list one task at a time, when a feature must ship in independently-verifiable slices, or when contracts in .forge/contracts/ need to be implemented against acceptance criteria.
triage-issue
Use when user reports a bug, wants to file an issue, mentions "triage", when investigating a production problem before fixing it, when planning a fix that needs a TDD-shaped GitHub issue, or when a bug needs root-cause analysis before assignment.
azure-cosmos-db-py
Build Azure Cosmos DB NoSQL services with Python/FastAPI following production-grade patterns. Use when implementing database client setup with dual auth (DefaultAzureCredential + emulator), service layer classes with CRUD operations, partition key strategies, parameterized queries, or TDD patterns for Cosmos. Triggers…