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/robdel12/orbitdock/rust-server-architecturenpx skills add Robdel12/OrbitDock --skill rust-server-architecturegit clone --depth 1 https://github.com/Robdel12/OrbitDockWrote 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/robdel12/orbitdock/rust-server-architecture)<a href="https://agentmods.dev/skills/robdel12/orbitdock/rust-server-architecture"><img src="https://agentmods.dev/badge/skills/robdel12/orbitdock/rust-server-architecture.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.00063 | $0.01504 |
| Opus 5 | $0.00032 | $0.00752 |
| Sonnet 5 | $0.00013 | $0.00301 |
| Haiku 4.5 | $0.00006 | $0.00150 |
Grade A, and why
rust-server-architecture 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 4d 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 — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rust Server Architecture
Use this skill when the work touches orbitdock-server/ and the quality of the design matters as much as the patch itself.
The goal is not just "make the tests pass." The goal is to make the server own durable truth, make invalid states hard or impossible to represent, and let the compiler force correct updates when the model changes.
Start Here
Before changing code, read only the docs that match the task:
docs/GETTING_STARTED.mdfor setup, build commands, and themake rust-*workflowdocs/ARCHITECTURE.mdfor server-authoritative state, typed-boundary expectations, and client/server guardrailsdocs/OPERATIONS.mdwhen schema, persistence, restore, deployment, or database troubleshooting are involveddocs/data-flow.mdwhen HTTP, WebSocket, session surfaces, or conversation rows are involved
If tests are part of the task, also use testing-philosophy.
Workflow
1. State the invariant first
Write down the user-facing or system-facing truth the server must protect.
Examples:
- "steer rows are not user prompts"
- "only the server owns durable approval state"
- "conversation rows get sequence numbers from one writer"
Do not start from the existing shape of the code if that shape is already suspicious.
2. Find the authority boundary
Decide which layer owns the truth:
domain/for business rules and pure state transitionsruntime/for orchestration, actors, registries, and command flowtransport/for HTTP and WebSocket mappinginfrastructure/for SQLite, filesystem, auth, crypto, and external concernsconnectors/for provider-specific translation
If multiple layers can independently "decide" the same thing, the design is probably wrong.
3. Make invalid states unrepresentable
Prefer:
- enums over booleans when there are meaningful modes
- dedicated structs or enum variants over "same shape, different meaning"
- newtypes over raw
Stringoru64when identity matters - typed params structs over long positional argument lists
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 178 lines · 63 tokens per session scan A f78ccaec8ac7
rust-server-architecture is a skill published in the GitHub repository Robdel12/OrbitDock (95 stars, last pushed 4mo ago), licensed MIT. It adds 63 tokens to every session and 1,504 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
swift-testing-pro
Writes, reviews, and improves Swift Testing code using modern APIs and best practices. Use when reading, writing, or reviewing projects that use Swift Testing.
rust-unit-tests
Write, improve, and run Rust unit tests in the warp Rust codebase.
os-rust-backend
Use when working on a Rust backend that follows the Open Software Network house style — the seven-crate Cargo workspace split (domain / services / persistence / providers / config / api / app) shared by os-accounts and os-platform (fellow). Trigger on: scaffolding a new service in this org ("like os-accounts"…
moai-lang-swift
Swift 6.0 enterprise development with async/await, SwiftUI, Combine, and Swift Concurrency. Advanced patterns for iOS, macOS, server-side Swift, and enterprise mobile applications with Context7 MCP integration.
swift-expert
Expert-level Swift development for iOS, macOS with SwiftUI, Combine, and modern Swift 5.9+.
next-rspack
Maintain @next/rspack-core and @next/rspack-binding packages. Use when editing rspack/package.json, rspack/crates/binding/Cargo.toml, rspack/rust-toolchain.toml, or packages/next-rspack/package.json. Covers upgrading @rspack/core npm version, rspack crate versions, Rust toolchain version, building and linking for…