continues is a command-line tool for moving an AI coding session from one coding agent to another while preserving conversation history, file changes, and working state. Developers use it when they need to continue work in a different tool, and the catalogue entries provide instructions for transferring sessions across supported agents.
Borrowing it
Nothing to install: this file belongs to yigitkonur/cli-continues. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/yigitkonur/cli-continues/main/.github/instructions/testing.instructions.mdgit clone --depth 1 https://github.com/yigitkonur/cli-continuesWrote 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/instructions/yigitkonur/cli-continues/testing)<a href="https://agentmods.dev/instructions/yigitkonur/cli-continues/testing"><img src="https://agentmods.dev/badge/instructions/yigitkonur/cli-continues/testing/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/instructions/yigitkonur/cli-continues/testing"><img src="https://agentmods.dev/badge/instructions/yigitkonur/cli-continues/testing.svg" alt="Reviewed on agentmods" width="80" 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.00425 | $0.00425 |
| Opus 5.5 | $0.00170 | $0.00170 |
| Sonnet 5.5 | $0.00085 | $0.00085 |
| Haiku 4.5 | $0.00042 | $0.00042 |
Grade A, and why
cli-continues testing.instructions.md 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 1mo 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
Test Review Guidelines
Fixture-Based Testing
- Tests must NOT require real session files on the local machine — use fixture factories from
src/__tests__/fixtures/index.ts - Each tool has a
create<Tool>Fixture()factory that creates a temp directory with realistic session data - Ground fixture schemas in real session file formats — verify field names against actual tool storage before creating fixtures; do not invent schemas
Conversion Coverage
unit-conversions.test.tsis the primary suite — it must cover all N tools × (N-1) target conversion paths- Adding a new tool requires: a fixture factory AND conversion tests covering all N-1 directions (as both source and target)
- PRs that add a new parser but do not update
unit-conversions.test.tsare incomplete
Test Quality
- Each test asserts ONE behavior — not multiple unrelated assertions bundled into a single test case
- Test names should describe the scenario:
should extract session summary from Claude JSONL - Tests must be independent — no shared mutable state between test cases
- Use
beforeAll/afterAllfor fixture setup and cleanup (create temp dir → run tests → delete temp dir)
Regression Tests
- Bug fixes must include a regression test that fails before the fix and passes after
- PRs that modify parser logic without touching any test file should be flagged — the CI
test-qualityjob will also flag this
Performance
- Test timeout is 30 seconds (
vitest.config.ts) — a test that times out indicates a parser with blocking or synchronous I/O - Excluded by vitest config:
e2e*,real-e2e*,stress*,injection*,parsers.test*— these require a real environment and are not run in CI - Node.js 22+ is required;
node:sqlitebuilt-in is used by OpenCode/Crush fixtures — do not add third-party SQLite deps
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.
- 1mo ago First seen · 36 lines · 425 tokens per session scan A bf74b5e3066e
cli-continues testing.instructions.md is an instructions file published in the GitHub repository yigitkonur/cli-continues (1,580 stars, last pushed 5mo ago), licensed MIT. It adds 425 tokens to every session, about $0.0017 per session on Opus 5.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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.