agentmods.dev

zeph copilot-instructions.md

Code-review rules for Zeph, a Rust AI-agent workspace made of many library packages and a command-line application.

In plain words
What is it for?
Reviewing Zeph changes, finding forbidden dependencies, checking TLS choices, validating workspace configuration, and enforcing Rust standards.
Why use it?
They give reviewers concrete checks for package dependencies, Rust style, optional components, transport security, and Cargo configuration.

Instructions file for GitHub Copilot

57 7d ago A scan 853 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/copilot-instructions
Clone the repo
git clone --depth 1 https://github.com/bug-ops/zeph

Made for: GitHub Copilot.

Per session 853 This file is loaded in full into every session.
When invoked 853 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.00853 $0.00853
Opus 5 $0.00426 $0.00426
Sonnet 5 $0.00171 $0.00171
Haiku 4.5 $0.00085 $0.00085

Measured yesterday against content hash 8ec7e3b44228, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

zeph copilot-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/copilot-instructions.md · 73 lines

How it starts

The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Copilot Code Review Instructions

Project Context

Zeph is a Rust AI agent workspace (Edition 2024, resolver 3) with 31 library crates under crates/ plus the zeph CLI binary. Review all changes against these standards.

Architecture Rules

  • zeph-core orchestrates all leaf crates; no reverse dependencies allowed
  • zeph-agent-context, zeph-agent-persistence, and zeph-agent-tools MUST NOT depend on zeph-core — the dependency runs zeph-core → these crates, never the reverse; flag any new zeph-core import added to them
  • zeph-durable is a Layer-0 infra crate (alongside zeph-db, zeph-common); it MUST NOT depend on zeph-llm, zeph-memory, zeph-core, zeph-sanitizer, or any business-layer crate
  • zeph-tui, zeph-a2a, zeph-acp, zeph-gateway, zeph-scheduler, and zeph-bench are feature-gated and optional
  • All dependencies defined in root [workspace.dependencies] with no features at workspace level
  • Crates inherit via workspace = true and specify features locally
  • TLS: rustls only — reject any openssl-sys introduction
  • Dependencies must be sorted alphabetically in Cargo.toml

Rust Code Standards

  • Edition 2024 native async traits — reject async-trait crate usage
  • unsafe code is not allowed — if you see any unsafe block, treat it as a blocking issue and call it out explicitly
  • Avoid .unwrap() and .expect() in non-test code — prefer ? with error propagation
  • Library crates use thiserror; application code uses anyhow with .context()
  • Logging via tracing crate only — reject log crate or println! in library code
  • Builder methods must return self and be annotated with #[must_use]
  • String parameters in constructors: accept impl Into<String>
  • Feature-gated modules: #[cfg(feature = "name")] on pub mod in lib.rs
  • Formatting: use rustfmt’s default settings (no project-specific rustfmt.toml)

Security Review (Critical)

  • Flag hardcoded secrets, API keys, tokens, or credentials
  • Flag SQL injection risks in SQLite queries (must use parameterized queries)
  • Flag command injection in shell executor (validate and sanitize inputs)
  • Flag path traversal in skill loader and file operations
  • Flag missing input validation at system boundaries
  • Flag XSS in any user-facing output
  • Verify deny.toml compliance for new dependencies

Read the full file on GitHub · 73 lines

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 · 73 lines · 853 tokens per session scan A 8ec7e3b44228

Subscribe to this mod's changes

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