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 instructions/nehliin/vortex/claude-mdgit clone --depth 1 https://github.com/Nehliin/vortexWrote 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/instructions/nehliin/vortex/claude-md)<a href="https://agentmods.dev/instructions/nehliin/vortex/claude-md"><img src="https://agentmods.dev/badge/instructions/nehliin/vortex/claude-md.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.00544 | $0.00544 |
| Opus 5 | $0.00272 | $0.00272 |
| Sonnet 5 | $0.00109 | $0.00109 |
| Haiku 4.5 | $0.00054 | $0.00054 |
Grade A, and why
vortex CLAUDE.md 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Architecture
Vortex is a high-performance BitTorrent client built in Rust using io-uring for asynchronous I/O. The project is structured as a Cargo workspace with four main components:
cli/: Terminal UI application using Ratatui for downloading torrents with DHT support. This is the primary client crate used to test that thebittorrentcrate can be used to create meaingful applications.bittorrent/: Core BitTorrent protocol implementation built on io-uring.
The bittorrent crate uses an event-driven architecture with io-uring for high-performance networking. Key modules include:
event_loop: Central event dispatcher managing connections and I/Opeer_comm: Peer connection management and protocol handlingpeer_comm/tests.rs: Peer protocol tests which require no prior setup (like podman containers)piece_selector: Download strategy and piece managementfile_store: Disk I/O operations for torrent data
Development Commands
Building and Testing
# Build all workspace members
cargo build
# Run the unit tests for the protocol logic
cargo nextest run peer_comm
# Run all tests including integration tests (requires Docker/Podman for Transmission containers)
just test
# Run specific integration test locally
just test-locally
# Format code
cargo fmt
# Lint code
cargo clippy --all-features --all-targets -- -D warnings
# Check dependencies for security issues and licensing
cargo deny check
Integration Test Environment Setup
Tests use Transmission containers for seeding torrents. The just test command automatically:
- Generates test files if needed
- Sets up Transmission seed containers via
scripts/transmission_containers.sh - Runs tests with
cargo nextest
Monitoring
Set up Grafana dashboard for metrics:
just setup-grafana
Key Dependencies and Constraints
- io-uring: Linux-specific async I/O interface (requires Linux)
- cargo-deny: Enforces dependency policies (see
deny.toml) - jemalloc: Used as global allocator in CLI
- Edition 2024: All crates use Rust edition 2024
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 · 68 lines · 544 tokens per session scan A e3117b6d479a
vortex CLAUDE.md is an instructions file published in the GitHub repository Nehliin/vortex (137 stars, last pushed yesterday), licensed BSD-3-Clause. It adds 544 tokens to every session, about $0.0027 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.