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 skills/dvnghiem/flowdeck/rust-patternsnpx skills add DVNghiem/FlowDeck --skill rust-patternsgit clone --depth 1 https://github.com/DVNghiem/FlowDeckWhat 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.00032 | $0.03336 |
| Opus 5 | $0.00016 | $0.01668 |
| Sonnet 5 | $0.00006 | $0.00667 |
| Haiku 4.5 | $0.00003 | $0.00334 |
Grade A, and why
rust-patterns scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
let data = fetch(url).await How it starts
The opening of the file, as written. The whole thing — 493 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rust Patterns Skill
Safe, idiomatic Rust for production systems. Covers the ownership model, trait system, and async patterns.
When to Activate
Activate when:
- Writing new Rust crates or services
- Reviewing Rust code for safety and idiom
- Fighting the borrow checker and looking for solutions
- Designing async services with Tokio
- Choosing between smart pointer types
Ownership and Borrowing — Mental Model
Every value has exactly one owner. When the owner goes out of scope, the value is dropped. References borrow a value without taking ownership.
The Three Rules
- Each value has exactly one owner.
- There can be any number of shared (
&T) references, OR exactly one exclusive (&mut T) reference — never both at the same time. - References must not outlive the value they point to.
fn main() {
let s1 = String::from("hello");
let s2 = s1; // ownership moved to s2
// println!("{s1}"); // compile error: s1 moved
let s3 = String::from("world");
let r1 = &s3; // shared borrow
let r2 = &s3; // another shared borrow — fine
println!("{r1} {r2}");
let mut s4 = String::from("mutable");
let r3 = &mut s4; // exclusive borrow
r3.push_str("!");
// let r4 = &s4; // compile error: s4 already mutably borrowed
}
Clone When You Need a Copy
// clone() is explicit and potentially expensive — use it knowingly
let original = vec![1, 2, 3];
let copy = original.clone();
// both are usable
// For cheap copies, implement Copy (stack-allocated types)
#[derive(Clone, Copy)]
struct Point { x: f64, y: f64 }
let p1 = Point { x: 1.0, y: 2.0 };
let p2 = p1; // copied, not moved — p1 still valid
Lifetime Annotations
The compiler infers lifetimes in most cases via elision rules. Annotate when the compiler cannot determine the relationship.
When Annotations Are Required
// Return value borrows from one of the arguments — annotate the relationship
fn longest<'a>(x: &'a str, y: &'a str) -> &'a str {
if x.len() > y.len() { x } else { y }
}
// Struct holding a reference must declare its lifetime
struct Excerpt<'a> {
text: &'a str,
}
impl<'a> Excerpt<'a> {
fn content(&self) -> &str {
self.text // lifetime elided — same as self's lifetime
}
}
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 · 493 lines · 32 tokens per session scan A 5c2d42d4e008
rust-patterns is a skill published in the GitHub repository DVNghiem/FlowDeck (24 stars, last pushed 13d ago), licensed MIT. It adds 32 tokens to every session and 3,336 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
oh-my-opencode-slim
Configure and improve oh-my-opencode-slim for the current user. Use when users want to tune agents, models, prompts, custom agents, skills, MCPs, presets, or plugin behavior. Also use when recurring workflow friction suggests a safe config or prompt improvement.
reflect
Review recent work, find repeated workflow patterns, and suggest reusable skills, agents, commands, config changes, or playbooks. Use when the user asks to learn from past sessions, improve recurring workflows, or identify what should be turned into reusable agent instructions.
clonedeps
Clone important project dependency source code into an ignored local workspace so OpenCode can inspect library internals. Use when the user asks to clone dependencies, inspect dependency/source internals, understand SDK/framework behavior from source, debug library implementation details, or make core dependency repos…
codemap
Generate comprehensive hierarchical codemaps for UNFAMILIAR repositories. Expensive operation - only use when explicitly asked for codebase documentation or initial repository mapping.
deepwork
High-cost orchestrator workflow for large, high-risk, multi-phase coding efforts with meaningful dependencies and review gates. Do not activate for routine multi-file changes.
worktrees
Manage Git worktrees as OMO safe isolated coding lanes for complex, risky, or parallel work.