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 commands/geoffjay/claude-plugins/tokio-migrategit 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-migrate)<a href="https://agentmods.dev/commands/geoffjay/claude-plugins/tokio-migrate"><img src="https://agentmods.dev/badge/commands/geoffjay/claude-plugins/tokio-migrate.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.00017 | $0.02435 |
| Opus 5 | $0.00009 | $0.01218 |
| Sonnet 5 | $0.00003 | $0.00487 |
| Haiku 4.5 | $0.00002 | $0.00244 |
Grade A, and why
tokio-migrate 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 — 430 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tokio Migrate Command
This command assists with migrating synchronous code to async Tokio, upgrading between Tokio versions, or converting from other async runtimes.
Arguments
$1- Migration type:sync-to-async,tokio-upgrade,runtime-switch(required)$2- Target file or directory (optional, defaults to current directory)$3- Additional context: Tokio version for upgrades, or source runtime for switches (optional)
Usage
/rust-tokio-expert:tokio-migrate sync-to-async src/handlers/
/rust-tokio-expert:tokio-migrate tokio-upgrade src/ 1.0
/rust-tokio-expert:tokio-migrate runtime-switch src/ async-std
Workflow
1. Sync to Async Migration
When migrating synchronous code to async Tokio:
Analysis Phase
-
Scan Target Files
- Use Glob to find all Rust files in target
- Read files and identify synchronous operations
- Detect blocking I/O operations
- Find CPU-intensive operations
- Identify thread spawning
-
Identify Conversion Candidates
- Functions with I/O operations (network, file, database)
- Functions that spawn threads
- Functions with sleep/delays
- Functions with synchronous HTTP clients
- Functions with blocking mutex operations
-
Analyze Dependencies
- Check
Cargo.tomlfor sync crates - Identify replacements (e.g.,
reqwestblocking → async) - Find database drivers needing async versions
- Check
Migration Phase
-
Invoke Agent
- Use Task tool with
subagent_type="rust-tokio-expert:tokio-pro" - Provide code context and migration plan
- Use Task tool with
-
Convert Functions to Async
The agent should transform:
Synchronous Function:
use std::fs::File; use std::io::Read; fn read_config(path: &str) -> Result<String, Error> { let mut file = File::open(path)?; let mut contents = String::new(); file.read_to_string(&mut contents)?; Ok(contents) }To Async:
use tokio::fs::File; use tokio::io::AsyncReadExt; async fn read_config(path: &str) -> Result<String, Error> { let mut file = File::open(path).await?; let mut contents = String::new(); file.read_to_string(&mut contents).await?; Ok(contents) }
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 · 430 lines · 17 tokens per session scan A c1267acd2d82
tokio-migrate is a command published in the GitHub repository geoffjay/claude-plugins (8 stars, last pushed 10mo ago), licensed MIT. It adds 17 tokens to every session and 2,435 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-08-31.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.