cli-continues ci.instructions.md

Repository instructions for reviewing a continuous-integration workflow. Continuous integration, or CI, automatically builds and tests code when changes are made.

In plain words
What is it for?
They guide action versioning, job permissions, Node.js versions, pnpm setup, frozen lockfiles, and the order for building and testing.
Why use it?
They reduce configuration, security, and compatibility mistakes in automated checks, including exposed secrets, overly broad permissions, and inconsistent package installation.

Instructions file for GitHub Copilot

Install

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.

agentmods
npx agentmods add instructions/yigitkonur/cli-continues/ci
Clone the repo
git clone --depth 1 https://github.com/yigitkonur/cli-continues

Made for: GitHub Copilot.

Per session 400 This file is loaded in full into every session.
When invoked 400 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00400 $0.00400
Opus 5 $0.00200 $0.00200
Sonnet 5 $0.00080 $0.00080
Haiku 4.5 $0.00040 $0.00040

Measured 2d ago against content hash 4ef46cc3b48d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 2d 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.

.github/instructions/ci.instructions.md · 37 lines

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 permissions explicitly 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.0 in package.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 pnpm exclusively — not npm ci or yarn — to stay consistent with pnpm-lock.yaml
  • Always run pnpm install --frozen-lockfile in CI to prevent accidental lockfile mutations
  • Use pnpm/action-setup@v4 for pnpm setup

Build and Test Order

  • Run pnpm run build (TypeScript compile) before pnpm testtsc validates type correctness; test failures may be caused by type errors caught at build time
  • The test-quality job 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-quality job should only run on pull_request events (not push to main)
Changes

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.

  1. 2d ago First seen · 37 lines · 400 tokens per session scan A 4ef46cc3b48d

Subscribe to this mod's changes

cli-continues ci.instructions.md is an instructions file published in the GitHub repository yigitkonur/cli-continues (1,479 stars, last pushed 3mo ago), licensed MIT. It adds 400 tokens to every session, about $0.0020 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-08-30.