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/ci.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/ci)<a href="https://agentmods.dev/instructions/yigitkonur/cli-continues/ci"><img src="https://agentmods.dev/badge/instructions/yigitkonur/cli-continues/ci/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/ci"><img src="https://agentmods.dev/badge/instructions/yigitkonur/cli-continues/ci.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.00400 | $0.00400 |
| Opus 5.5 | $0.00160 | $0.00160 |
| Sonnet 5.5 | $0.00080 | $0.00080 |
| Haiku 4.5 | $0.00040 | $0.00040 |
Grade A, and why
cli-continues ci.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
CI Workflow Review Guidelines
Security
- Pin action versions to at least a named tag (
actions/checkout@v4); prefer full commit SHA for security-critical actions - Set
permissionsexplicitly on any job that needs elevated access (e.g.,pull-requests: write) — do not rely on repository-wide defaults - Never print secret values to logs — use GitHub's secret masking for dynamic secrets
# Prefer explicit permissions scoping
permissions:
pull-requests: write
contents: read
Node.js Version Requirements
- Node 22 is the minimum supported version (
engines.node >= 22.0.0inpackage.json) - The CI matrix must include at least Node 22 and the latest even-numbered LTS — do not drop below 22
node:sqlite(built-in, Node 22.5+) is used by OpenCode and Crush parsers — do not add third-party SQLite packages
Package Manager
- Use
pnpmexclusively — notnpm cioryarn— to stay consistent withpnpm-lock.yaml - Always run
pnpm install --frozen-lockfilein CI to prevent accidental lockfile mutations - Use
pnpm/action-setup@v4for pnpm setup
Build and Test Order
- Run
pnpm run build(TypeScript compile) beforepnpm test—tscvalidates type correctness; test failures may be caused by type errors caught at build time - The
test-qualityjob posts a PR comment summarizing test counts and flags source-file changes without corresponding test changes — do not remove this job without an equivalent replacement - The
test-qualityjob should only run onpull_requestevents (not push tomain)
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 · 37 lines · 400 tokens per session scan A 4ef46cc3b48d
cli-continues ci.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 400 tokens to every session, about $0.0016 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.