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 vynazevedo/first-plan --skill lens-rustgit clone --depth 1 https://github.com/vynazevedo/first-planWrote 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/vynazevedo/first-plan/lens-rust)<a href="https://agentmods.dev/skills/vynazevedo/first-plan/lens-rust"><img src="https://agentmods.dev/badge/skills/vynazevedo/first-plan/lens-rust.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.1 | $0.00056 | $0.00835 |
| Opus 5 | $0.00028 | $0.00417 |
| Sonnet 5 | $0.00011 | $0.00167 |
| Haiku 4.5 | $0.00006 | $0.00084 |
Grade A, and why
first-plan-lens-rust 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 7d 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lens Rust
Detecção fina
| Sinal | Variante |
|---|---|
[[bin]] em Cargo.toml ou src/main.rs |
Binário |
[lib] em Cargo.toml ou src/lib.rs |
Lib |
axum / actix-web / rocket / warp em deps |
HTTP API |
tonic em deps |
gRPC |
tokio em deps |
Async runtime tokio |
async-std em deps |
Async runtime async-std |
clap em deps + bin |
CLI |
tauri em deps |
Tauri (desktop) |
bevy |
Game/3D |
[workspace] em Cargo.toml |
Workspace (monorepo Rust) |
Extração de padrões
Estrutura
src/main.rsousrc/bin/<name>.rssrc/lib.rs+ módulos- Workspaces - quais crates, dependências entre eles
tests/integration testsexamples/exemplosbenches/benchmarks
Error handling
thiserror(typed errors)anyhow(boxed errors em apps)?operator usage- Custom Error enums
Async
- Runtime: tokio vs async-std vs smol
Send + Syncconstraints- Spawning tasks (
tokio::spawn) - Channels (
tokio::sync::mpsc,crossbeam)
Macros
derivemacros customizados (sinal: dependências de proc-macro crates)macro_rules!definidos no projeto
Testing
#[test]unit tests inlinetests/integrationcriterionpara benchmarksproptest,quickcheck(property testing)mockall(mocks)wiremock(HTTP mocks)
Web
axum:
- Handlers como funções
async fn(...) -> impl IntoResponse - Extractors (
State,Json,Path,Query) - Routers compostos
actix-web:
- Handlers com
web::Data,web::Json - App factory
Logging
tracingecosystem (tracing + tracing-subscriber + tracing-opentelemetry)logcrate + env_logger (legacy)
Build / config
cargo-make,justem vez de Makefileclippy.toml,rustfmt.toml- Edition (2018, 2021, 2024)
MSRV(minimum supported Rust version)
Output
Padrão. Atenção:
02-conventions/errors.md- thiserror vs anyhow vs custom02-conventions/di.md- Rust geralmente usa State/Context structs em vez de DI clássico
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.
- 7d ago First seen · 108 lines · 56 tokens per session scan A be03a0d3e76e
first-plan-lens-rust is a skill published in the GitHub repository vynazevedo/first-plan (23 stars, last pushed 13d ago), licensed MIT. It adds 56 tokens to every session and 835 once invoked, about $0.0003 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 skills, from other repositories
google-antigravity-sdk-rust
Design, implement, and debug autonomous AI agents and multi-agent systems in Rust using the Google Antigravity (AGY) Rust SDK. ACTIVATE this skill when the user wants to create, configure, or orchestrate Google Antigravity agents in Rust.
bevy-ecs
Structure a Bevy app around its Entity Component System: build the App with plugins, define Component/Resource types, write systems with Query/Res/Commands, filter and order systems, and use the Time resource for frame-rate-independent motion. Use when building or debugging a Bevy game in Rust — when the user mentions…
rust-crate-ci
Load before editing any Rust crate in this repo (currently runners/swarm-sandbox-runner). Covers the mandatory local validation gate, common rustfmt/clippy pitfalls, and Windows-specific Rust correctness patterns that CI enforces but are hard to catch locally without a Windows toolchain.
rust-patterns
Rust: ownership, lifetimes, async (Tokio), Result/anyhow/thiserror, traits, unsafe. Triggers: Rust, borrow checker, lifetime, Tokio, cargo, trait, impl, Result, unsafe, clippy.
rust-engineer
Acquire expert Rust developer specialisation in rust systems programming, memory safety, and zero-cost abstractions. Masters ownership patterns, async programming, and performance optimisation for mission-critical applications.
rust-rules
Rust coding rules: style, patterns, security, testing. Triggers: .rs, Cargo.toml, Cargo.lock, Tokio, Axum, Serde, clippy, cargo test.