agentmods.dev

zeph rust.instructions.md

A set of Rust coding and review guidelines covering lint settings, asynchronous code, types, error handling, and tests.

In plain words
What is it for?
Use it when reviewing Rust files, choosing async patterns, organizing public types, or writing unit and integration tests.
Why use it?
It gives developers consistent rules for writing and reviewing Rust code, including safer error handling and project-specific conventions.

Instructions file for GitHub Copilot

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

Made for: GitHub Copilot.

Per session 321 This file is loaded in full into every session.
When invoked 321 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.00321 $0.00321
Opus 5 $0.00161 $0.00161
Sonnet 5 $0.00064 $0.00064
Haiku 4.5 $0.00032 $0.00032

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

Security

Grade A, and why

zeph rust.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/rust.instructions.md · 31 lines

What it actually says

Rust File Review

Lints

  • Workspace Clippy lints clippy::all + clippy::pedantic are configured as warnings in Cargo.toml
  • Review policy: prefer #![forbid(unsafe_code)] in crates and reject new unsafe blocks unless strictly justified and well-documented
  • Review policy: avoid unwrap() and expect() in non-test code; require explicit error handling instead

Async Patterns

  • Use native async trait methods (Edition 2024)
  • Use Pin<Box<dyn Future<...> + Send + '_>> only when trait object safety requires it
  • Runtime: tokio with #[tokio::main] entry point

Type Conventions

  • Type aliases for complex pinned types: type ChatStream = Pin<Box<dyn Stream<...> + Send>>
  • Re-export public API at crate root via pub use in lib.rs
  • Serde: #[serde(tag = "kind")] for enums with data, #[serde(rename_all = "camelCase")] for A2A types

Test Code

  • Unit tests in inline #[cfg(test)] mod tests at module end
  • Mock types (MockProvider, MockChannel) inside #[cfg(test)] blocks implementing the real trait
  • Use tempfile for filesystem fixtures, testcontainers for Qdrant
  • Tests sharing state require #[serial] attribute
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 · 31 lines · 321 tokens per session scan A 454a47d92910

Subscribe to this mod's changes

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