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 skills add dewtech-technologies/dare-method --skill 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/skills/dewtech-technologies/dare-method/dare-rust-workspace)<a href="https://agentmods.dev/skills/dewtech-technologies/dare-method/dare-rust-workspace"><img src="https://agentmods.dev/badge/skills/dewtech-technologies/dare-method/dare-rust-workspace/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/skills/dewtech-technologies/dare-method/dare-rust-workspace"><img src="https://agentmods.dev/badge/skills/dewtech-technologies/dare-method/dare-rust-workspace.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.00081 | $0.02662 |
| Opus 5.5 | $0.00032 | $0.01065 |
| Sonnet 5.5 | $0.00016 | $0.00532 |
| Haiku 4.5 | $0.00008 | $0.00266 |
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 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 — 276 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DARE — Rust Workspace Skill (single-crate vs multi-crate)
Use esta skill em dois momentos:
- Design / Blueprint: projeto Rust novo na stack
rust-axum. Decida desde o início se ele nasce single-crate ou em workspace multi-crate. - Migração: projeto Rust single-crate já existente que cresceu demais e está doendo. Proponha o plano de migração.
Regra geral: comece simples, migre quando os critérios objetivos abaixo aparecerem. Workspace é a estrutura idiomática Rust para projetos maduros, mas é overengineering para o "hello world".
Cenário A — Decisão na fase Design/Blueprint
Comece single-crate quando TODOS forem verdadeiros
- Apenas 1 binário (HTTP server).
- Estimativa de < 30 arquivos
.rsnosrc/. - 1–2 sistemas externos (apenas DB; ou DB + cache).
- Equipe ≤ 2 devs.
- Nenhum requisito de deploy independente para subcomponentes.
Comece workspace multi-crate quando QUALQUER um for verdadeiro
- ≥ 2 binários previstos (API + worker; API + admin; API + CLI).
- Múltiplos sistemas externos (3+: PG + Redis + Rabbit + Qdrant + Neo4j…).
- Deploy independente desejado (workers em pods separados no k8s).
- Fronteiras arquiteturais críticas (domain puro sem HTTP/DB; SDK publicável; cliente compartilhado com outros projetos).
- Equipe ≥ 3 devs trabalhando em paralelo.
Layout convencional para workspace
Use o prefixo do projeto (<p>) — ex: wa- para wa-business-api,
agent- para agent-ai.
projeto/
├── Cargo.toml # workspace root
├── docker-compose.yml
├── Dockerfile
├── crates/
│ ├── <p>-domain/ (lib) # entities puras
│ ├── <p>-config/ (lib) # AppConfig::from_env()
│ ├── <p>-db/ (lib) # sqlx pool, migrations
│ ├── <p>-cache/ (lib) # redis/moka
│ ├── <p>-queue/ (lib) # lapin/kafka
│ ├── <p>-crypto/ (lib) # bcrypt, jwt
│ ├── <p>-services/ (lib) # business logic, sem HTTP
│ ├── <p>-integrators/ (lib) # clientes externos (LLM, Stripe…)
│ ├── <p>-api/ (bin + lib) # HTTP server
│ ├── <p>-worker-<X>/ (bin) # 1 binário por tipo de worker
│ ├── <p>-admin/ (bin) # CLI admin
│ └── <p>-e2e/ (tests) # integration 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.
- 1mo ago First seen · 276 lines · 81 tokens per session scan A 5c0b2f6d6afa
dare-rust-workspace is a skill published in the GitHub repository dewtech-technologies/dare-method (5 stars, last pushed 3mo ago), licensed MIT. It adds 81 tokens to every session and 2,662 once invoked, about $0.0003 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-31.
Other skills, from other repositories
beautifulsoup-parsing
Expert guidance for HTML/XML parsing using BeautifulSoup in Python with best practices for DOM navigation, data extraction, and efficient scraping workflows.
llamaindex-development
Expert guidance for LlamaIndex development including RAG applications, vector stores, document processing, query engines, and building production AI applications.
aspnet-core
Guidelines for ASP.NET Core web development covering API design, authentication, caching, and best practices.
express-typescript
Guidelines for building robust APIs with Express.js and TypeScript, covering middleware patterns, routing, and security best practices.
hono-typescript
Guidelines for building edge-first, high-performance APIs with Hono and TypeScript for Cloudflare Workers, Deno, Bun, and Node.js.
koa-typescript
Guidelines for building modern APIs with Koa.js and TypeScript, featuring the onion middleware model and async/await patterns.