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/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-leptos)<a href="https://agentmods.dev/commands/dewtech-technologies/dare-method/dare-rust-leptos"><img src="https://agentmods.dev/badge/commands/dewtech-technologies/dare-method/dare-rust-leptos/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/commands/dewtech-technologies/dare-method/dare-rust-leptos"><img src="https://agentmods.dev/badge/commands/dewtech-technologies/dare-method/dare-rust-leptos.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.00000 | $0.02452 |
| Opus 5 | $0.00000 | $0.01226 |
| Sonnet 5 | $0.00000 | $0.00490 |
| Haiku 4.5 | $0.00000 | $0.00245 |
Grade A, and why
dare-rust-leptos 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 5d 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 — 270 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/dare-rust-leptos
Guia de desenvolvimento Leptos para projetos DARE. Cobre decisão de variante, idioms obrigatórios, antipatterns, tipos compartilhados e templates de tasks.
Como usar
/dare-rust-leptos ← decide variante + configura workspace
/dare-rust-leptos --csr ← guia específico para CSR + trunk
/dare-rust-leptos --fullstack ← guia específico para SSR + cargo-leptos
/dare-rust-leptos --shared-types ← padrão cfg_attr para tipos server + WASM
1. Decisão de variante: CSR vs Fullstack
| Critério | CSR (trunk) | Fullstack (cargo-leptos) |
|---|---|---|
| SEO necessário | ❌ | ✅ |
| Time-to-interactive crítico | ❌ | ✅ |
| Dashboard interno / admin | ✅ | ✅ |
| Backend Axum existente | indiferente | ✅ integração direta |
| Simplicidade de deploy | ✅ arquivos estáticos (CDN) | ⚠️ binário Axum |
Server functions (#[server]) |
❌ não existe | ✅ |
Regra de ouro:
- Se o projeto vive atrás de login e SEO não importa → CSR
- Se precisa de SEO, carregamento inicial rápido, ou server functions → Fullstack
- Se já tem
rust-axumcomo backend no monorepo → Fullstack (workspace unificado)
2. Ferramentas — nunca misturar
| Variante | Build | Dev server | Test |
|---|---|---|---|
| CSR | trunk build --release |
trunk serve |
cargo test --workspace |
| Fullstack | cargo leptos build --release |
cargo leptos watch |
cargo test --workspace |
⚠️
cargo leptos testnão existe. Use semprecargo test --workspace. ⚠️ Não usetrunkpara fullstack nemcargo leptospara CSR — ferramentas erradas para o target errado.
3. Idioms obrigatórios Leptos 0.7
Estado reativo
// ✅ Fine-grained signals — só re-renderiza o que usa o signal
let (count, set_count) = signal(0);
let doubled = move || count.get() * 2; // derived (memo inline)
// Para estado complexo ou compartilhado entre componentes:
let count = RwSignal::new(0); // read + write em um só
Dados assíncronos
// ✅ Resource — fetch declarativo, integra com Suspense
let user = Resource::new(|| user_id(), |id| async move { fetch_user(id).await });
// ✅ Suspense — loading state automático
view! {
<Suspense fallback=|| view! { <p>"Loading..."</p> }>
{move || user.get().map(|u| view! { <p>{u.name}</p> })}
</Suspense>
}
// ❌ Nunca — Effect que faz fetch (re-executa em todo render)
Effect::new(move |_| { spawn_local(async { fetch_user(id).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.
- 5d ago First seen · 270 lines · 0 tokens per session scan A 67dbd98e11ff
dare-rust-leptos 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,452 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
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.
wcag-audit
Accessibility audit based on WCAG 2.1/2.2 and the axe-core reference.
ccboard-install
Install or update ccboard.
health
Command "health" from Vimalk0703/shipworthy, covering part 1: plugin installation health and part 2: project health.
rust:audit-layer-boundaries
Analyze layer boundary definitions in Rust codebases, identifying mixed responsibilities and violations.
rust:tauri:health
Comprehensive health check of a running Tauri application.