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 skills add fakoli/fakoli-plugins --skill rust-network-modulegit clone --depth 1 https://github.com/fakoli/fakoli-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/skills/fakoli/fakoli-plugins/rust-network-module)<a href="https://agentmods.dev/skills/fakoli/fakoli-plugins/rust-network-module"><img src="https://agentmods.dev/badge/skills/fakoli/fakoli-plugins/rust-network-module/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/skills/fakoli/fakoli-plugins/rust-network-module"><img src="https://agentmods.dev/badge/skills/fakoli/fakoli-plugins/rust-network-module.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.00043 | $0.00546 |
| Opus 5.5 | $0.00017 | $0.00218 |
| Sonnet 5.5 | $0.00009 | $0.00109 |
| Haiku 4.5 | $0.00004 | $0.00055 |
Grade A, and why
rust-network-module 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 1mo 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.
What it actually says
Rust Network Module
Start with the actual repository: read its instructions, Cargo.toml, lockfile, toolchain/MSRV settings, a neighboring networking module, and existing shutdown/configuration/tests. Preserve the crate's layout, error types, runtime, visibility, feature flags, tracing conventions, and wiring. Do not assume a nat464 dependency list, require directory modules, or register everything in main.rs/try_join!.
Choose the smallest relevant starting point in assets. Resolve these files relative to this installed skill directory, not the user's project. Copy/adapt only the required templates into the requested crate:
| Asset | Purpose |
|---|---|
listener.rs.tmpl |
TCP accept loop with caller-owned binding/shutdown, bounded handler count, task observation, and bounded drain |
protocol.rs.tmpl |
Executable example framing and parser/reply logic; replace with the actual protocol contract |
tests.rs.tmpl |
Assertions for the example protocol's bytes, fragmentation, invalid/truncated input, timeout, and write failure |
mod.rs.tmpl |
Optional module root; use a flat file if that matches the project |
Substitute __NAME__ with a snake_case identifier, __TYPE__ with a PascalCase type prefix, __PRIMARY__ with the actual child module, and __DESCRIPTION__ with its purpose. The example protocol is not SOCKS5. TCP assets do not implement UDP, ICMP, DNS racing, or HTTP: use patterns to choose those architectures without pretending a TCP scaffold implements them.
Implement the requested behavior before claiming completion. Define frame/size limits, deadlines, overload policy, shutdown ownership, and error handling appropriate to the real feature. Keep binding explicit; [::] is not a portable guarantee of dual-stack behavior. A handshake interrupted during a partial read must be discarded or resumed from saved state, not blindly restarted.
Wire through the crate's existing lifecycle. Add only missing dependencies/features compatible with its MSRV; template requirements and verification commands are in the README. Run formatting, the relevant tests, and the project's normal checks. Include observable success, error/protocol, and shutdown paths when implementing a server. Tests use port 0 or in-memory duplex streams and deadlines; empty writes or successful compilation alone do not verify networking behavior.
What ships with it
6 files 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.
- 1mo ago Changed · -49 lines · -35 tokens per session 78ea2990247d
- 1mo ago First seen · 73 lines · 78 tokens per session scan A daaf0aeceb01
rust-network-module is a skill published in the GitHub repository fakoli/fakoli-plugins (4 stars, last pushed 25d ago), licensed MIT. It adds 43 tokens to every session and 546 once invoked, about $0.0002 per session on Opus 5.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 skills, from other repositories
rust-ops
Rust development patterns, ownership, async, error handling, and ecosystem. Use for: rust, cargo, ownership, borrow checker, lifetime, tokio, serde, trait, Result, Option, async rust, crate, derive, impl, enum, pattern matching, Arc, Mutex, Send, Sync, thiserror, anyhow, clap, axum, sqlx, reqwest, rayon, tracing.
axum-web-framework
Complete guide for Axum web framework including routing, extractors, middleware, state management, error handling, and production deployment.
rust-systems-programming
Complete guide for Rust systems programming including ownership, borrowing, concurrency, async programming, unsafe code, and performance optimization.
agent-django-fastapi-expert
Specialist subagent: Django ORM, Django REST Framework, FastAPI async patterns, and Pydantic v2 specialist. Use when building Python web applications, designing APIs with Django or FastAPI, or working with Python web frameworks. Trigger phrases: Django, FastAPI, DRF, Django REST Framework, Pydantic, ORM, queryset…
rust-systems
Build and upgrade Rust services, CLI and systems components with explicit error, async and resource contracts. Use when working on Rust ownership, concurrency, serialization or unsafe boundaries; preserve MSRV and edition compatibility unless their migration is requested.
agent-go-expert
Specialist subagent: Go concurrency, error handling, stdlib patterns, Chi/Echo web frameworks specialist. Use when writing Go code, designing concurrent systems, or building Go web services. Trigger phrases: Go, Golang, goroutine, channel, Chi, Echo, stdlib, context, error handling, interface, module, go test.