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 rules/platinoff/poolai/rust-toolchain-baselinegit clone --depth 1 https://github.com/platinoff/poolAIWhat 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.00000 | $0.00212 |
| Opus 5 | $0.00000 | $0.00106 |
| Sonnet 5 | $0.00000 | $0.00042 |
| Haiku 4.5 | $0.00000 | $0.00021 |
Grade A, and why
rust-toolchain-baseline 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 2d 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 Toolchain Baseline
- For dependency, feature, or build config edits, preserve compatibility with installed baseline:
rustc 1.92.0cargo 1.92.0- target profile from
rust-toolchain.tomland.cargo/config.toml
Required validation when changing project config
- If
Cargo.toml,Cargo.lock,rust-toolchain.toml, or.cargo/config.tomlis updated:- verify
cargo check - verify
cargo clippy --all-features -- -D warningswhen practical - document important toolchain impacts in
docs/development/
- verify
Dependency hygiene
- Prefer latest compatible crates unless project policy pins a version.
- Remove unused dependencies/features after updates to keep CI stable and faster.
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.
- 2d ago First seen · 25 lines · 0 tokens per session scan A 49559eee9e4d
rust-toolchain-baseline is a cursor rule published in the GitHub repository platinoff/poolAI (4 stars, last pushed 9d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 212 tokens. 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 cursor rules, from other repositories
rust
When working on imageflow, we want to preserve comments in the code - ALWAYS - since they help us remember corner cases. Always repeat them back out into the new code. And always load /imageflowtypes/src/lib.rs into memory, since we use it in every rust file.
core
Core STT/TTS abstraction layer documentation.
collection-iterators
How to implement and test iterators on APAS-VERUS collection modules.
table-of-contents-standard
Standard section ordering and TOC format for Verus source files.
ptt-commands
Commands for building and running Proof Time Tests (PTTs).
xlit-macros
Use XLit! macros (SetLit!, RelationLit!, etc.) to construct test values.