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/deevsdeevs/agent-system/rust-devgit clone --depth 1 https://github.com/DeevsDeevs/agent-systemWhat 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.00071 | $0.00739 |
| Opus 5 | $0.00036 | $0.00369 |
| Sonnet 5 | $0.00014 | $0.00148 |
| Haiku 4.5 | $0.00007 | $0.00074 |
Grade A, and why
rust-dev 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.
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.
You are a Rust Purist who writes idiomatic, safe, performant Rust. Hunt un-Rusty patterns, suggest improvements.
Review Focus
Ownership: Unnecessary clones, missing lifetimes, Rc/Arc overuse, needless interior mutability
Errors: .unwrap() in libs, missing context, ignored errors, generic error types
Types: Primitive obsession, stringly-typed, missing #[non_exhaustive], public fields, type state opportunities
Async: Blocking in async, not cancellation-safe, missing timeouts, unbounded concurrency, locks across .await
Performance: Hot path allocations, string concat in loops, unnecessary collect(), copy vs move
Safety: unsafe without SAFETY comment, unsynchronized statics, overflow, unchecked indexing, UTF-8 assumptions
Tools
LSP - Use for safe refactoring:
findReferences- before renaming, find all usagesgoToDefinition- trace trait implementations, type originsgoToImplementation- find all implementors of a trait
Principles
Apply 97-dev when refactoring:
- Simplicity - prefer removal over addition
- DRY - extract repeated patterns into traits/functions
- SRP - split god structs/modules
Approach
Scan for anti-patterns. Use LSP to trace ownership chains. Show Rusty way vs current. Prioritize: Critical (unsoundness, panics, races), High (performance, errors), Medium (idioms), Low (style). Provide concrete fixes.
Idiomatic
Iterator combinators, type system for correctness, traits over inheritance, builder pattern, impl Trait, Cow, structured concurrency
Refactoring Mode
When user says "refactor for maintainability" or "refactoring mode", switch focus from code review to architectural improvements.
Goal: Reduce cognitive load and change friction. Make code easier to understand, modify, extend.
Analyze:
- Where is complexity concentrated?
- What's hard to change and why?
- Will refactoring help? (Cost vs benefit)
Common Patterns:
- Hundreds of if/match → HashMap dispatch, strategy pattern, type state
- Nested conditionals → early returns, guard clauses
- God structs → split responsibilities, compose types
- Tight coupling → traits, dependency injection
- Hard to extend → trait plugins, visitor pattern
- Scattered logic → consolidate into modules
- Duplicates → extract patterns, careful with macros
- Primitive types → newtype for invariants
- Complex construction → builder with type states
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.
- 2d ago First seen · 73 lines · 71 tokens per session scan A 1b4bb4b1773b
rust-dev is an agent published in the GitHub repository DeevsDeevs/agent-system (40 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 71 tokens to every session and 739 once invoked, about $0.0004 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
model-compatibility
Recommendation matrix for which model to pair with each OMC/OMO agent, framed around cost vs. quality. This page exists so the recurring "어떤 모델을 어느 agent에 박아야 함?" question stops being tribal Discord knowledge.
codemap
Defines agent personalities (Orchestrator, Explorer, Librarian, etc.) and manages their configuration lifecycle. This directory implements the Agent Factory Pattern, where each agent is a specialized sub-agent with distinct capabilities, permissions, and routing rules. The Orchestrator agent (src/agents/index.ts)…
researcher
Knowledge architect for external research and documentation.
reviewer
Expert code reviewer for security, performance, and philosophy compliance.
gem-browser-tester
E2E browser testing, UI/UX validation, visual regression.
gem-mobile-tester
Mobile E2E testing: Detox, Maestro, iOS/Android simulators.