agentmods.dev

zeph ci.instructions.md

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

57 7d ago A scan 188 tokens original MIT
View the source file bug-ops/zeph
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/bug-ops/zeph/ci
Clone the repo
git clone --depth 1 https://github.com/bug-ops/zeph

Made for: GitHub Copilot.

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. 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.00188 $0.00188
Opus 5 $0.00094 $0.00094
Sonnet 5 $0.00038 $0.00038
Haiku 4.5 $0.00019 $0.00019

Measured yesterday against content hash 763dfbeef965, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 yesterday.

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. yesterday 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 (57 stars, last pushed 7d ago), licensed MIT. It adds 188 tokens to every session, about $0.0009 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.

Code reviewDebuggingLLMTestingai-agentclaudecliollamarust
Related

Other instructions, from other repositories

Chimeraforge CLAUDE.md

Instructions for Sahil170595/Chimeraforge, covering claude.md — chimeraforge, rule 1 -- assertive by default, research, data, and validation discipline, project overview and quick reference.

Sahil170595/Chimeraforge · 10,677 tokens

Chimeraforge AGENTS.md

Instructions for Sahil170595/Chimeraforge, covering agents.md — chimeraforge, rule 1 -- assertive by default, research, data, and validation discipline, verify gates and engineering standards (chimera-wide).

Sahil170595/Chimeraforge · 1,933 tokens

rag-ferrite AGENTS.md

AGENTS.md instructions for lelabdev/rag-ferrite, covering rag-ferrite — moteur rag personnel (rust), stack, architecture, décisions d'architecture and structure du code.

lelabdev/rag-ferrite · 3,369 tokens

ollama CLAUDE.md

Instructions for ollama/ollama: See AGENTS.md for the shared agent instructions for this repository.

ollama/ollama · 21 tokens

agentgateway copilot-instructions.md

Instructions for agentgateway/agentgateway: Do not check for, speculate about, or report compilation errors during code review. Compilation diagnostics from review are frequently incorrect; rely on CI to detect and report compilation failures.

agentgateway/agentgateway · 41 tokens

mq commit.instructions.md

Instructions for harehare/mq: Use the following format for commit messages.

harehare/mq · 167 tokens