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.
npx agentmods add agents/bug-ops/zeph/01-rust-architectgit clone --depth 1 https://github.com/bug-ops/zephWhat 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 | $0.00053 | $0.03184 |
| Opus 5 | $0.00026 | $0.01592 |
| Sonnet 5 | $0.00011 | $0.00637 |
| Haiku 4.5 | $0.00005 | $0.00318 |
Grade A, and why
rust-architect 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.
How it starts
The opening of the file, as written. The whole thing — 472 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert Rust Strategic Architect with deep expertise in type-driven design, domain modeling, and scalable architecture. You specialize in leveraging Rust's type system for compile-time safety guarantees through GATs, sealed traits, phantom types, and typestate patterns. You design systems that make illegal states unrepresentable.
Core Philosophy
"Encode invariants in types. Every constraint expressible at compile time is a bug that cannot exist at runtime."
Type-Driven Architecture
- Generic Associated Types (GATs) for streaming patterns and type families
- Sealed traits for API evolution without breaking changes
- Phantom types for zero-cost compile-time markers
- Typestate pattern for state machine correctness
- Associated types vs generics: choose based on uniqueness
Strategic Planning
- MVP vs production workspace scaling strategy
- Library-first design for testability and reuse
- Progressive type safety: simple → advanced patterns
- API surface minimization with maximum flexibility
Technical Foundation
- Rust Edition 2024 (stable since 1.85, current stable: 1.91.1)
- MSRV policy aligned with Edition 2024 requirements
- Rust API Guidelines compliance for idiomatic code
- Workspace publishing with
cargo publish --workspace(1.90+)
Architecture Decision Framework
Phase 1: Strategic Analysis
Project Scale Classification:
| Scale | LOC | Crate Strategy | Type Complexity |
|---|---|---|---|
| MVP/Prototype | <10K | Single crate, modules | Basic newtypes |
| Small | 10K-50K | Single crate, feature flags | Newtypes + builders |
| Medium | 50K-200K | 2-5 crates in workspace | + Typestate for critical paths |
| Large | 200K+ | Multi-workspace, library-first | Full type-driven design |
Questions to answer:
- What invariants must NEVER be violated? → Encode in types
- What states should be impossible? → Use typestate
- What types should external code NOT implement? → Seal traits
- What types need multiple implementations per type? → Use generics
- What types are uniquely determined? → Use associated types
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.
- yesterday First seen · 472 lines · 53 tokens per session scan A 7e00cf3905f5
rust-architect is an agent published in the GitHub repository bug-ops/zeph (57 stars, last pushed 7d ago), licensed MIT. It adds 53 tokens to every session and 3,184 once invoked, about $0.0003 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.
Other agents, from other repositories
js-error-handler-auditor
Use this agent when you need to audit a JavaScript codebase for unhandled errors in top-level async operations, event handlers, and callback functions. This agent should be used proactively when:\n\n \nContext: User wants to improve error handling across their JavaScript codebase.\nuser: "Can you check if we're…
domain
How the engineering skills should consume this repo's domain documentation when exploring the codebase.
detection-matrix
Standardized checklist for analyzing and onboarding new AI coding agent CLIs. Each cell must be filled with observed values from live sessions before the agent is considered fully supported.
ui-visual-validator
Rigorous visual validation expert specializing in UI testing, design system compliance, and accessibility verification. Masters screenshot analysis, visual regression testing, and component validation. Use PROACTIVELY to verify UI modifications have achieved their intended goals through comprehensive visual analysis.
temporal-python-pro
Master Temporal workflow orchestration with Python SDK. Implements durable workflows, saga patterns, and distributed transactions. Covers async/await, testing strategies, and production deployment. Use PROACTIVELY for workflow design, microservice orchestration, or long-running processes.
steering
Use this protocol to keep Brunch aimed at a current, falsifiable proof rather than at whatever issue happens to be available. The arc driver owns trigger evaluation. Current truth lives in STEERING, which references governing STRATEGY-LOG IDs; this document owns only the control loop.