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/security.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/security)<a href="https://agentmods.dev/instructions/yigitkonur/cli-continues/security"><img src="https://agentmods.dev/badge/instructions/yigitkonur/cli-continues/security/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/security"><img src="https://agentmods.dev/badge/instructions/yigitkonur/cli-continues/security.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.00419 | $0.00419 |
| Opus 5.5 | $0.00168 | $0.00168 |
| Sonnet 5.5 | $0.00084 | $0.00084 |
| Haiku 4.5 | $0.00042 | $0.00042 |
Grade A, and why
cli-continues security.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
Security Review Guidelines — Core Utilities
Command Injection Prevention (resume.ts)
- External processes must be spawned with
spawn()and arguments as an array — NEVERexec()with string interpolation - Session IDs and file paths from parsed sessions are user-controlled and may contain shell metacharacters (
;,|,&,$, backticks) — they must always be array elements, never embedded in a shell string
// Avoid — command injection if sessionId contains ; or | or $()
exec(`claude --resume ${sessionId}`);
// Prefer — safe regardless of sessionId content
spawn('claude', ['--resume', sessionId], { stdio: 'inherit' });
Forward Flag Security (forward-flags.ts)
--dangerously-skip-permissions(Claude) and--dangerously-bypass-approvals-and-sandbox(Codex) must ONLY be set when the source session explicitly requested auto-approve behavior- Flag precedence is security-critical: auto-approve > full-auto > sandbox > ask-for-approval — deviations from this order could grant unintended permissions in the target tool
- Never map a "plan mode" flag or any scheduling flag to auto-approve behavior
Handoff Output Safety (markdown.ts)
- Do NOT embed secrets, API keys, tokens, or environment variable values in handoff markdown output
- Tool activity summaries (shell command output, file diffs) may contain sensitive data — the verbosity config caps limit exposure; do not bypass these caps
- Home directory paths in handoff output must be tildified (
~/) usingsafePath()— never expose the full absolute home path
General
- No hardcoded credentials, API keys, or tokens anywhere in source files
- User-supplied paths (session file paths,
cwdvalues) must not be passed to shell execution without sanitization — usespawn()with array args only
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 · 419 tokens per session scan A 25ab7dc2f8df
cli-continues security.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 419 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.