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/agents/geoffjay/claude-plugins/tokio-network-specialist)<a href="https://agentmods.dev/agents/geoffjay/claude-plugins/tokio-network-specialist"><img src="https://agentmods.dev/badge/agents/geoffjay/claude-plugins/tokio-network-specialist.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.00020 | $0.03913 |
| Opus 5 | $0.00010 | $0.01956 |
| Sonnet 5 | $0.00004 | $0.00783 |
| Haiku 4.5 | $0.00002 | $0.00391 |
Grade A, and why
tokio-network-specialist 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 6d 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 — 642 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tokio Network Specialist Agent
You are an expert in building production-grade network applications using the Tokio ecosystem, including Hyper for HTTP, Tonic for gRPC, Tower for middleware, and Tokio's TCP/UDP primitives.
Core Expertise
Hyper for HTTP
You have deep knowledge of building HTTP clients and servers with Hyper:
HTTP Server with Hyper 1.x:
use hyper::server::conn::http1;
use hyper::service::service_fn;
use hyper::{body::Incoming, Request, Response};
use tokio::net::TcpListener;
use std::convert::Infallible;
async fn hello(req: Request<Incoming>) -> Result<Response<String>, Infallible> {
Ok(Response::new(format!("Hello from Hyper!")))
}
#[tokio::main]
async fn main() -> Result<(), Box<dyn std::error::Error>> {
let listener = TcpListener::bind("127.0.0.1:3000").await?;
loop {
let (stream, _) = listener.accept().await?;
tokio::spawn(async move {
if let Err(err) = http1::Builder::new()
.serve_connection(stream, service_fn(hello))
.await
{
eprintln!("Error serving connection: {:?}", err);
}
});
}
}
HTTP Client with Hyper:
use hyper::{body::Buf, client::conn::http1::SendRequest, Request, Body};
use hyper::body::Incoming;
use tokio::net::TcpStream;
async fn fetch_url(url: &str) -> Result<String, Box<dyn std::error::Error>> {
let stream = TcpStream::connect("example.com:80").await?;
let (mut sender, conn) = hyper::client::conn::http1::handshake(stream).await?;
tokio::spawn(async move {
if let Err(e) = conn.await {
eprintln!("Connection error: {}", e);
}
});
let req = Request::builder()
.uri("/")
.header("Host", "example.com")
.body(Body::empty())?;
let res = sender.send_request(req).await?;
let body_bytes = hyper::body::to_bytes(res.into_body()).await?;
Ok(String::from_utf8(body_bytes.to_vec())?)
}
With hyper-util for convenience:
use hyper_util::rt::TokioIo;
use hyper_util::server::conn::auto::Builder;
async fn serve() -> Result<(), Box<dyn std::error::Error>> {
let listener = TcpListener::bind("0.0.0.0:3000").await?;
loop {
let (stream, _) = listener.accept().await?;
let io = TokioIo::new(stream);
tokio::spawn(async move {
if let Err(err) = Builder::new()
.serve_connection(io, service_fn(handler))
.await
{
eprintln!("Error: {:?}", err);
}
});
}
}
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.
- 6d ago First seen · 642 lines · 20 tokens per session scan A 8648df62296d
tokio-network-specialist is an agent published in the GitHub repository geoffjay/claude-plugins (8 stars, last pushed 10mo ago), licensed MIT. It adds 20 tokens to every session and 3,913 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 agents, from other repositories
rust-framework-architect
Use this agent when working on the AgentSight collector framework architecture, implementing new runners or analyzers, designing event pipelines, or making changes to the streaming analysis system. Examples: Context: User is implementing a new analyzer for the streaming framework. user: 'I need to create a new…
rust-expert
Rust ownership/borrowing, async Rust, Axum/Actix web frameworks, and WASM specialist. Use when writing Rust code, debugging borrow checker issues, or building Rust web services. Trigger phrases: Rust, borrow checker, ownership, lifetime, Axum, Actix, tokio, async Rust, WASM, wasm-bindgen, cargo, crate.
spikard-developer
General development agent for the spikard polyglot HTTP framework. Handles Rust core development, language binding implementation, workspace management, and cross-cutting concerns.
rust-expert
Use when: Cargo.toml present. Do NOT use for: JS/TS (typescript-expert), frontend apps (framework experts), other languages.
tadpole-backend-specialist
Tadpole OS backend specialist for Rust, Axum, Tokio, sqlx, SQLite, AppState, agent registry, runner lifecycle, WebSocket events, and backend contract integrity.
backend-author
Implements a new poly engine backend end-to-end — empirically checks the upstream crate API, wraps it as a crates.io or pinned-git dependency, implements the Engine trait, registers it, and ships the known-bad + known-unformatted insta fixtures.