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 commands/dewtech-technologies/dare-method/dare-rust-workspacegit clone --depth 1 https://github.com/dewtech-technologies/dare-methodWrote 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/commands/dewtech-technologies/dare-method/dare-rust-workspace)<a href="https://agentmods.dev/commands/dewtech-technologies/dare-method/dare-rust-workspace"><img src="https://agentmods.dev/badge/commands/dewtech-technologies/dare-method/dare-rust-workspace.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.02021 |
| Opus 5 | $0.00000 | $0.01010 |
| Sonnet 5 | $0.00000 | $0.00404 |
| Haiku 4.5 | $0.00000 | $0.00202 |
Grade A, and why
dare-rust-workspace 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 — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/dare-rust-workspace
Decisão e migração de Cargo workspace multi-crate para projetos Rust/Axum. Cobre dois cenários:
- Cenário A — Design/Blueprint: decidir desde o início se o projeto nasce single-crate ou workspace.
- Cenário B — Migração: propor plano de PRs incrementais para transformar um projeto single-crate maduro em workspace.
Como usar
/dare-rust-workspace # análise contextual (lê BLUEPRINT/src/)
/dare-rust-workspace --design # foco em decisão para projeto novo
/dare-rust-workspace --migrate # foco em plano de migração
O que fazer
1) Detectar o cenário
- Se existe
DARE/BLUEPRINT.mdmas osrc/ainda não existe ou tem < 5 arquivos → Cenário A (decisão) - Se
src/tem > 30 arquivos.rsou múltiplas subpastas top-level → Cenário B (migração) - Caso intermediário (15–30 arquivos) → mostrar os critérios e perguntar ao usuário
2) Cenário A — Decisão na fase Design/Blueprint
Aplique os critérios:
Comece single-crate quando TODOS forem verdadeiros:
- Apenas 1 binário (HTTP server)
- < 30 arquivos
.rsesperados - 1–2 sistemas externos (DB; ou DB + cache)
- Equipe ≤ 2 devs
- Sem deploy independente para subcomponentes
Comece workspace quando QUALQUER for verdadeiro:
- ≥ 2 binários previstos (API + worker; API + admin)
- ≥ 3 sistemas externos (PG + Redis + Rabbit + Qdrant + Neo4j…)
- Deploy independente desejado (workers em pods separados)
- Fronteiras arquiteturais críticas (domain puro; SDK publicável)
- Equipe ≥ 3 devs em paralelo
Layout recomendado para workspace (use <p> como prefixo do projeto):
projeto/
├── Cargo.toml # workspace root
├── crates/
│ ├── <p>-domain/ (lib) # entities puras
│ ├── <p>-config/ (lib)
│ ├── <p>-db/ (lib)
│ ├── <p>-cache/ (lib)
│ ├── <p>-queue/ (lib)
│ ├── <p>-services/ (lib) # business logic
│ ├── <p>-integrators/ (lib) # clientes externos
│ ├── <p>-api/ (bin+lib) # HTTP server
│ ├── <p>-worker-<X>/ (bin) # 1 binário por worker
│ └── <p>-e2e/ (tests)
└── xtask/ # scripts em Rust
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 · 210 lines · 0 tokens per session scan A 8ddb8eb6b6ce
dare-rust-workspace is a command published in the GitHub repository dewtech-technologies/dare-method (5 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,021 tokens. 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-09-03.
Other commands, from other repositories
worktree
Git Worktree Setup for RTK.
audit-crate
Audit a single crate (used by /audit coordinator or standalone).
rust-critique
Deep code critique — read the target Rust code and apply the full review process. Evaluates soundness, ownership, error handling, type design, async correctness, performance, and architecture. Think like a senior Rust engineer giving honest feedback.
rust-teach
One-time setup that scans your Rust project, understands its patterns and conventions, and writes a Rust-specific context section to your CLAUDE.md. Run once per project to establish persistent Rust guidelines.
rust-harden
Harden Rust code — replace unwrap with proper error handling, add safety comments to unsafe blocks, enable overflow checks, validate inputs at boundaries. The defensive hardening pass.
rust-types
Strengthen the type system — replace primitive obsession with newtypes, booleans with enums, stringly-typed APIs with domain types. Make illegal states unrepresentable.