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.
curl -O https://raw.githubusercontent.com/bug-ops/zeph/main/AGENTS.mdgit clone --depth 1 https://github.com/bug-ops/zephWrote 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/bug-ops/zeph/agents-md)<a href="https://agentmods.dev/instructions/bug-ops/zeph/agents-md"><img src="https://agentmods.dev/badge/instructions/bug-ops/zeph/agents-md/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/bug-ops/zeph/agents-md"><img src="https://agentmods.dev/badge/instructions/bug-ops/zeph/agents-md.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.02109 | $0.02109 |
| Opus 5.5 | $0.00844 | $0.00844 |
| Sonnet 5.5 | $0.00422 | $0.00422 |
| Haiku 4.5 | $0.00211 | $0.00211 |
Grade A, and why
zeph AGENTS.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.
How it starts
The opening of the file, as written. The whole thing — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
Zeph is a Rust workspace (Cargo.toml) with the CLI entrypoint in src/ and domain crates in crates/ (for example: zeph-core, zeph-llm, zeph-memory, zeph-tools, zeph-tui).
Top-level integration tests live in tests/, while crate-specific tests and benches live under each crate’s tests/ and benches/ directories. Documentation sources are in book/src/ (mdBook), runtime defaults are in config/default.toml, and container assets are in docker/.
Do not create git worktrees inside this repository. Create separate worktrees only under the sibling directory ../worktrees/.
Specifications (MANDATORY)
All feature and system specifications live in specs/. Compliance is non-negotiable.
- Before implementing any feature: read the relevant spec in
specs/and the system invariants inspecs/001-system-invariants/spec.md. - Before modifying any subsystem: read the corresponding spec document. The
## Key InvariantsandNEVERsections define hard constraints — violating them requires an explicit architectural decision, not just a code review. - Index:
specs/README.md— maps every subsystem to its spec file. - Constitution:
specs/constitution.md— project-wide non-negotiable rules that apply to every change. - If a spec is missing or outdated for the area you are changing, create or update it before writing code.
Agent Operating Notes
AGENTS.md is the primary instruction file for all coding agents (Codex, Copilot, etc.). .claude/CLAUDE.md and .claude/rules/* are Claude-specific or supplemental context — not the primary source of operating rules.
Path-specific instructions for GitHub Copilot live in .github/instructions/*.instructions.md with applyTo frontmatter.
- Use
cargo nextest runas the default test runner. - Keep Rust changes compatible with Edition 2024 and MSRV
1.98. - Prefer zero-warning
clippy; avoidunwrap/expectin production code when proper error propagation is possible. - Any user-facing change must update relevant docs, config defaults, and
CHANGELOG.md([Unreleased]section). - For new functionality, provide all integration points: config section, CLI subcommand/argument, TUI command palette entry,
--initwizard,--migrate-configmigration step, live testing playbook in.local/testing/playbooks/, and coverage row in.local/testing/coverage-status.md. - In the TUI, every background operation (LLM inference, memory search, tool execution, MCP connection, etc.) must have a visible spinner with a short, descriptive status message.
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 · 92 lines · 2,109 tokens per session scan A 492d2e32dd71
zeph AGENTS.md is an instructions file published in the GitHub repository bug-ops/zeph (65 stars, last pushed 5d ago), licensed MIT. It adds 2,109 tokens to every session, about $0.0084 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.