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
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/pawurb/hotpath-rsnpx agentmods add skills/pawurb/hotpath-rs/hotpath_bumpWrote 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/pawurb/hotpath-rs/hotpath_bump)<a href="https://agentmods.dev/skills/pawurb/hotpath-rs/hotpath_bump"><img src="https://agentmods.dev/badge/skills/pawurb/hotpath-rs/hotpath_bump.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 44 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00073 | $0.00754 |
| Opus 5 | $0.00036 | $0.00377 |
| Sonnet 5 | $0.00015 | $0.00151 |
| Haiku 4.5 | $0.00007 | $0.00075 |
Grade A, and why
hotpath_bump 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 8d 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bump hotpath Version
Bump the hotpath version number in every place it appears. The user provides the new version (e.g. 0.25.0); if only major.minor is given, assume patch 0.
Two formats are used:
- Exact version (
X.Y.Z, e.g.0.25.0) - all Cargo.toml entries - Major.minor only (
X.Y, e.g.0.25) - all other references
1. Cargo.toml files - exact version X.Y.Z
Update the version field in the [package] section of each crate:
crates/hotpath/Cargo.tomlcrates/hotpath-macros/Cargo.tomlcrates/hotpath-meta/Cargo.tomlcrates/hotpath-macros-meta/Cargo.toml
Update the version in the four [workspace.dependencies] entries in the root Cargo.toml:
hotpath-macros = { path = "./crates/hotpath-macros", version = "X.Y.Z" }
hotpath = { path = "./crates/hotpath", version = "X.Y.Z" }
hotpath-meta = { path = "./crates/hotpath-meta", version = "X.Y.Z" }
hotpath-macros-meta = { path = "./crates/hotpath-macros-meta", version = "X.Y.Z" }
All four crates always share the same version; never bump one without the others.
2. Other references - major.minor X.Y
-
../hotpath-backend/src/config/middleware.rs(separate repo, sibling directory):const TEMPLATE_VARS: &[(&str, &str)] = &[("{{HOTPATH_VERSION}}", "X.Y")]; -
skills/hotpath_init/SKILL.md- every version occurrence (hotpath = "X.Y",hotpath = { version = "X.Y", ... }) -
README.md- every version occurrence (cargo install hotpath --version '^X.Y',hotpath = "X.Y")
3. Verify
Search for stragglers with the old version, excluding lockfiles, target dirs, and third-party code:
rg -n 'OLD_X\.OLD_Y' Cargo.toml README.md skills/ crates/hotpath/Cargo.toml crates/hotpath-macros/Cargo.toml crates/hotpath-meta/Cargo.toml crates/hotpath-macros-meta/Cargo.toml
rg -n 'OLD_X\.OLD_Y' ../hotpath-backend/src/config/middleware.rs
Ignore matches that are not hotpath version references (other dependencies may coincidentally share the number). Then run cargo check so Cargo.lock picks up the new versions.
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.
- 8d ago First seen · 62 lines · 73 tokens per session scan A c7aecff1ff91
hotpath_bump is a skill published in the GitHub repository pawurb/hotpath-rs (1,711 stars, last pushed yesterday), licensed MIT. It adds 73 tokens to every session and 754 once invoked, about $0.0004 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 skills, from other repositories
find-postgres-bug
Find latent bugs in a local PostgreSQL source tree (RELxxSTABLE branch or HEAD) the way a core hacker does: build a heavily-poisoned debug instance (cassert + cache-discard + -O0/-ggdb3 + core dumps), fuzz it (sqlsmith) until the backend crashes, triage the core into a minimal reproducer (MRE), git-bisect the…
github-api-pagination
How to use gh api with pagination to retrieve all results from GitHub REST API endpoints, including PRs and issues.
performance-optimizer
Systematic performance profiling and optimization for Python and web backends — measure first, fix second, verify the fix.
benchmarking
A guide to benchmarking, which means measuring how quickly and reliably a computer, disk, database, or service performs under test. It uses tools such as sysbench and fio.
http-load-tester
A command-line tool for gradually increasing the number of simultaneous requests sent to an HTTP service, such as an API or website.
performance-profiler
Application performance profiling - runtime snapshots, benchmarking, memory analysis, startup timing, and bottleneck detection.