zeph: Instructions file for GitHub Copilot

.github/instructions/ci.instructions.md

zeph ci.instructions.md is an instructions file for GitHub Copilot from bug-ops/zeph. It costs 188 tokens per session, scanned A, original, MIT.

Review rules for continuous integration, the automated process that checks code when changes are proposed. They cover pipeline order, tests, code quality checks, security, and supported operating systems.

In plain words
What is it for?
Reviewing CI configuration, checking Rust projects across Ubuntu, macOS, and Windows, verifying coverage, and inspecting workflow security.
Why use it?
They help catch missing checks, unsafe workflow settings, skipped safeguards, and incomplete approval gates before code is merged.

Instructions file for GitHub Copilot

Written for GitHub Copilot: a Copilot instructions file.

This is bug-ops/zeph's own configuration. It tells GitHub Copilot how to work on zeph itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything zeph configures →

Reuse

Borrowing it

Nothing to install: this file belongs to bug-ops/zeph. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/bug-ops/zeph/main/.github/instructions/ci.instructions.md
Clone the repo
git clone --depth 1 https://github.com/bug-ops/zeph

Made for: GitHub Copilot.

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.

agentmods badge for zeph ci.instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/bug-ops/zeph/ci/github.svg)](https://agentmods.dev/instructions/bug-ops/zeph/ci)
Your own site
<a href="https://agentmods.dev/instructions/bug-ops/zeph/ci"><img src="https://agentmods.dev/badge/instructions/bug-ops/zeph/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.

agentmods 80×15 button for zeph ci.instructions.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/bug-ops/zeph/ci"><img src="https://agentmods.dev/badge/instructions/bug-ops/zeph/ci.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 188 This file is loaded in full into every session.
When invoked 188 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00188 $0.00188
Opus 5.5 $0.00075 $0.00075
Sonnet 5.5 $0.00038 $0.00038
Haiku 4.5 $0.00019 $0.00019

Measured 1mo ago against content hash 763dfbeef965, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

zeph 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.

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

What it actually says

CI Workflow Review

Pipeline Structure

  • Required structure: lint-fmt → lint-clippy → (test, integration, coverage) in parallel
  • docker-build-and-scan must be present and treated as a required job
  • Gate job ci-status must require all checks (including docker-build-and-scan)
  • Test matrix: ubuntu, macos, windows
  • Coverage via cargo-llvm-cov uploaded to codecov

Security

  • Reject pull_request_target trigger without explicit justification
  • Prefer stable, reputable action versions (e.g., major tags like v2, v6); pin to full SHAs for security-sensitive workflows when feasible
  • Reject secrets in workflow logs or step outputs
  • Reject --no-verify or hook-skipping flags
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. 1mo ago First seen · 21 lines · 188 tokens per session scan A 763dfbeef965

Subscribe to this mod's changes

zeph ci.instructions.md is an instructions file published in the GitHub repository bug-ops/zeph (65 stars, last pushed 5d ago), licensed MIT. It adds 188 tokens to every session, about $0.0008 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.

Related

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).

microsoft/vscode · 9,715 tokens

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.

vercel/next.js · 7,786 tokens

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).

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

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).

microsoft/vscode · 2,731 tokens

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.

denoland/deno · 3,077 tokens