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/geoffjay/claude-pluginsWrote 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/geoffjay/claude-plugins/tokio-scaffold)<a href="https://agentmods.dev/commands/geoffjay/claude-plugins/tokio-scaffold"><img src="https://agentmods.dev/badge/commands/geoffjay/claude-plugins/tokio-scaffold/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/geoffjay/claude-plugins/tokio-scaffold"><img src="https://agentmods.dev/badge/commands/geoffjay/claude-plugins/tokio-scaffold.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.00016 | $0.01671 |
| Opus 5 | $0.00008 | $0.00835 |
| Sonnet 5 | $0.00003 | $0.00334 |
| Haiku 4.5 | $0.00002 | $0.00167 |
Grade A, and why
tokio-scaffold 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 8d 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 — 248 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tokio Scaffold Command
This command scaffolds new Tokio-based Rust projects with modern structure, proper dependencies, error handling patterns, tracing infrastructure, and testing setup.
Arguments
$1- Project name (required)$2- Project type:http-server,grpc-server,tcp-server,cli, orlibrary(optional, defaults tolibrary)
Usage
/rust-tokio-expert:tokio-scaffold my-service http-server
/rust-tokio-expert:tokio-scaffold my-cli cli
/rust-tokio-expert:tokio-scaffold my-lib library
Workflow
-
Validate Arguments
- Check that project name is provided
- Validate project type if provided
- Ensure target directory doesn't already exist
-
Invoke Agent
- Use Task tool with
subagent_type="rust-tokio-expert:tokio-pro" - Pass project name and type to the agent
- Use Task tool with
-
Agent Instructions
The agent should create a complete project structure based on the type:
For HTTP Server Projects
Create:
-
Cargo.tomlwith dependencies:- tokio with full features
- axum for HTTP framework
- tower and tower-http for middleware
- serde and serde_json for serialization
- tracing and tracing-subscriber for logging
- anyhow and thiserror for error handling
- sqlx (optional) for database
- config for configuration management
-
src/main.rswith:- Runtime setup with tracing
- Router configuration
- Graceful shutdown handling
- Health check endpoints
-
src/handlers/mod.rswith example HTTP handlers -
src/error.rswith custom error types -
src/config.rswith configuration loading -
src/telemetry.rswith tracing setup -
tests/integration_test.rswith API integration tests -
.env.examplewith configuration template -
README.mdwith usage instructions
For gRPC Server Projects
Create:
Cargo.tomlwith:- tokio with full features
- tonic and tonic-build
- prost for protobuf
- tower for middleware
- tracing infrastructure
- error handling crates
-
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.
- 8d ago First seen · 248 lines · 16 tokens per session scan A f2cc37afd9f2
tokio-scaffold is a command published in the GitHub repository geoffjay/claude-plugins (8 stars, last pushed 10mo ago), licensed MIT. It adds 16 tokens to every session and 1,671 once invoked, about $0.0001 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-09-03.
Other commands, from other repositories
review-rust
Focused Rust/Tauri backend review with rust-backend-architect (Primary Owner).
generate-docs
Generates a Rust-scoped symbol inventory to assist agents in understanding the public API surface of the workspace.
docs
Fetch Rust API documentation from docs.rs.
cargo-bench
Command "cargo-bench" from olorehq/olore, covering cargo-bench(1), name, synopsis, description and working directory of benchmarks.
cargo-build
Command "cargo-build" from olorehq/olore, covering cargo-build(1), name, synopsis, description and options.
cargo-check
Command "cargo-check" from olorehq/olore, covering cargo-check(1), name, synopsis, description and options.