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/claude-plugins/15-rust-arch-analystgit clone --depth 1 https://github.com/bug-ops/claude-pluginsWhat 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.00077 | $0.00371 |
| Opus 5 | $0.00039 | $0.00186 |
| Sonnet 5 | $0.00015 | $0.00074 |
| Haiku 4.5 | $0.00008 | $0.00037 |
Grade A, and why
rust-arch-analyst 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 35 lines · 77 tokens per session scan A 547d8735a143
rust-arch-analyst is an agent published in the GitHub repository bug-ops/claude-plugins (11 stars, last pushed 8d ago), with no licence file. It adds 77 tokens to every session and 371 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
rust-coding-author
Author or refactor Rust functions in the agentenv-core / agentenv-cli crates with TDD, idiomatic error handling, and the project's source-driven pipeline conventions. Use when the user asks to add, rewrite, or extend a function in crates/agentenv-core/ or crates/agentenv-cli/ — especially new readers, writers…
rust-developer
Use this agent when the user explicitly requests help with Rust development tasks. This includes building Rust projects, creating libraries or binaries, implementing async patterns with Tokio, working with ownership/borrowing, running cargo commands, or reviewing Rust code. Context: User is starting a new Rust project…
rust-async-safety-reviewer
Reviews Rust async code for tokio + libsql + axum concurrency hazards. Use after changes touching tokio::spawn, axum handlers, libsql connection usage, or any Send/Sync boundaries. Read-only — produces findings, does not edit.
docs
Generate documentation from code. Creates README files, API references, and inline documentation based on code analysis.
code-reviewer
Code review specialist for Rust projects. Use after completing features or before PRs to ensure memory safety, idiomatic Rust, and adherence to project standards.
meerkat-rust-zealot
Use this agent when code changes have been made and need architectural review before being committed or merged. This agent should be invoked after any significant code modification to ensure alignment with Meerkat's architecture and Rust idioms.\n\nExamples:\n\n- user: "I've added a new caching layer to meerkat-cli…