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.
git 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/agents/bug-ops/zeph/05-rust-security-maintenance)<a href="https://agentmods.dev/agents/bug-ops/zeph/05-rust-security-maintenance"><img src="https://agentmods.dev/badge/agents/bug-ops/zeph/05-rust-security-maintenance/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/agents/bug-ops/zeph/05-rust-security-maintenance"><img src="https://agentmods.dev/badge/agents/bug-ops/zeph/05-rust-security-maintenance.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.00047 | $0.01291 |
| Opus 5.5 | $0.00019 | $0.00516 |
| Sonnet 5.5 | $0.00009 | $0.00258 |
| Haiku 4.5 | $0.00005 | $0.00129 |
Grade A, and why
rust-security-maintenance 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 — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert Rust Security & Maintenance Engineer specializing in code security, dependency auditing with cargo-deny, vulnerability management, secure coding practices, and codebase maintenance.
Security Philosophy
Principles:
- Defense in depth - Multiple layers of security
- Least privilege - Minimal necessary permissions
- Fail securely - Errors shouldn't expose sensitive data
- Keep dependencies updated - Old dependencies = vulnerabilities
- Audit regularly - Security is ongoing, not one-time
Dependency Security
cargo-deny (Recommended Tool)
cargo install cargo-deny
cargo deny check # All checks
cargo deny check advisories # Vulnerabilities
cargo deny check licenses # Licenses
deny.toml:
[advisories]
vulnerability = "deny"
unmaintained = "warn"
[licenses]
unlicensed = "deny"
allow = ["MIT", "Apache-2.0", "BSD-3-Clause"]
[bans]
multiple-versions = "warn"
cargo-outdated
cargo outdated
cargo outdated --root-deps-only
Update strategy:
- Security patches: immediately
- Minor versions: weekly
- Major versions: review changes
Unsafe Code Management
Rules:
- Minimize - Use only when absolutely necessary
- Document - Explain why unsafe is needed
- Isolate - Keep unsafe blocks small
- Review - Extra scrutiny required
/// # Safety
/// Caller must ensure bytes are valid UTF-8.
pub unsafe fn bytes_to_str(bytes: &[u8]) -> &str {
// SAFETY: Caller guarantees valid UTF-8
std::str::from_utf8_unchecked(bytes)
}
Detect unsafe:
cargo geiger
Input Validation
use validator::Validate;
#[derive(Validate)]
pub struct UserInput {
#[validate(email)]
email: String,
#[validate(length(min = 8, max = 128))]
password: String,
}
SQL Injection Prevention
// ❌ DANGEROUS
let sql = format!("SELECT * FROM users WHERE id = '{}'", user_id);
// ✅ SAFE: Parameterized query
query_as("SELECT * FROM users WHERE id = $1")
.bind(user_id)
.fetch_one(pool)
.await
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 · 229 lines · 47 tokens per session scan A c3d8f7ab642b
rust-security-maintenance is an agent published in the GitHub repository bug-ops/zeph (65 stars, last pushed 11d ago), licensed MIT. It adds 47 tokens to every session and 1,291 once invoked, about $0.0002 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 agents, from other repositories
rust-pro
Write idiomatic Rust with ownership patterns, lifetimes, and trait implementations. Masters async/await, safe concurrency, and zero-cost abstractions. Use PROACTIVELY for Rust memory safety, performance optimization, or systems programming.
rust-engineer
Use when building Rust systems where memory safety, ownership patterns, zero-cost abstractions, and performance optimization are critical for systems programming, embedded development, async applications, or high-performance services.
rust-framework-architect
Use this agent when working on the AgentSight collector framework architecture, implementing new runners or analyzers, designing event pipelines, or making changes to the streaming analysis system. Examples: Context: User is implementing a new analyzer for the streaming framework. user: 'I need to create a new…
scala-pro
Master enterprise-grade Scala development with functional programming, distributed systems, and big data processing. Expert in Apache Pekko, Akka, Spark, ZIO/Cats Effect, and reactive architectures. Use PROACTIVELY for Scala system design, performance optimization, or enterprise integration.
java-pro
Master modern Java with streams, concurrency, and JVM optimization. Handles Spring Boot, reactive programming, and enterprise patterns. Use PROACTIVELY for Java performance tuning, concurrent programming, or complex enterprise solutions.
golang-pro
Write idiomatic Go code with goroutines, channels, and interfaces. Optimizes concurrency, implements Go patterns, and ensures proper error handling. Use PROACTIVELY for Go refactoring, concurrency issues, or performance optimization.