hotpath-rs is a Rust profiler that measures where programs spend time, use CPU and memory, wait on I/O, and perform database, HTTP, or asynchronous operations. Rust developers use it to locate performance bottlenecks and inspect timing, allocation, and async-flow data.
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/pawurb/hotpath-rs/agents-mdgit clone --depth 1 https://github.com/pawurb/hotpath-rsWrote 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/pawurb/hotpath-rs/agents-md)<a href="https://agentmods.dev/instructions/pawurb/hotpath-rs/agents-md"><img src="https://agentmods.dev/badge/instructions/pawurb/hotpath-rs/agents-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.02336 | $0.02336 |
| Opus 5 | $0.01168 | $0.01168 |
| Sonnet 5 | $0.00467 | $0.00467 |
| Haiku 4.5 | $0.00234 | $0.00234 |
Grade A, and why
hotpath-rs AGENTS.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 5d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This file provides guidance to AI agent when working with code in this repository.
Project Overview
hotpath-rs is a lightweight, feature-gated Rust profiler that tracks function execution time, memory allocations, channels, streams, futures, locks, SQL queries, HTTP requests, byte-level I/O, and threads. All instrumentation is behind the hotpath Cargo feature: with it off, every macro is a no-op and no dependencies are compiled.
Workspace layout:
crates/hotpath- Main library with profiling runtime, reporting, metrics/MCP servers, and the TUI/CLI binariescrates/hotpath-macros- Procedural macros (#[measure],#[main],#[future_fn], ...)crates/test-*- One integration-test crate per instrumented subsystem or third-party integration; the current list is themembersarray in the rootCargo.tomltest-toastyis NOT a workspace member: toasty's rusqlite and the workspace's sqlx-sqlite have conflictinglinks = "sqlite3"values, so it's built viacargo run --manifest-path crates/test-toasty/Cargo.toml ...
crates/hotpath-meta/crates/hotpath-macros-meta- Copies of hotpath used to profile the profiler itself (not intended for external use)docs/- mdBook source for the hotpath.rs documentation site (the Axum web server that builds/serves it lives in a separate private repo at../hotpath-backend)
Reference Docs
The dev_docs point to where things are defined in source and record gotchas the code can't show - read them only when a task needs the specifics:
dev_docs/features.md- Where feature flags, macros, the builder API, and env vars are defined, plus behavior gotchasdev_docs/architecture.md- Background workers, metrics/MCP server code map, CPU sampling internals and pitfallsdev_docs/tui.md- TUI build/usage, console code map, layout conventionsdev_docs/testing.md- Integration-test patterns (crates/hotpath/tests/): polling the metrics endpoint vs parsing the guard-drop JSON report, example code, and test-file conventions. Read before writing or modifying an integration test.CONTRIBUTING.md- Meta-crate mirroring (syncmeta skill), self and overhead benchmark commands (just bench_meta,just compare_meta, per-subsystembenchmark_*examples), samply tracing, the exact CI check commands to run locally, and docs build prerequisites
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.
- 5d ago First seen · 104 lines · 2,336 tokens per session scan A 6db0deb49fa2
hotpath-rs AGENTS.md is an instructions file published in the GitHub repository pawurb/hotpath-rs (1,708 stars, last pushed today), licensed MIT. It adds 2,336 tokens to every session, about $0.0117 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
codspeed AGENTS.md
AGENTS.md instructions for CodSpeedHQ/codspeed, covering agents.md, common development commands, building and testing, build the project and build in release mode.
spark-history-cli AGENTS.md
Instructions for yaooqinn/spark-history-cli, covering agents.md, project overview, repository structure, key development guidelines and making changes.
codspeed CLAUDE.md
Claude Code instructions for CodSpeedHQ/codspeed, a project described as: CodSpeed is the all-in-one performance testing toolkit. Optimize code performance and catch regressions early.
mobilegym AGENTS.md
Instructions for Purewhiter/mobilegym, covering agents.md, project overview, type-checking strategy, eslint and with data graph generation.
ClawBench AGENTS.md
AGENTS.md instructions for TIGER-AI-Lab/ClawBench, covering clawbench -- agent context, what this is, project structure, setup and 2. configure at least one model.
openbench AGENTS.md
Instructions for minghinmatthewlam/openbench, covering openbench — agent context, local execution context, what openbench is, execution ownership and product goals (the two things we are building toward).