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.
git clone --depth 1 https://github.com/zifeo/ladeWrote 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/rules/zifeo/lade/sandbox-cargo)<a href="https://agentmods.dev/rules/zifeo/lade/sandbox-cargo"><img src="https://agentmods.dev/badge/rules/zifeo/lade/sandbox-cargo/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/rules/zifeo/lade/sandbox-cargo"><img src="https://agentmods.dev/badge/rules/zifeo/lade/sandbox-cargo.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.00239 | $0.00239 |
| Opus 5.5 | $0.00096 | $0.00096 |
| Sonnet 5.5 | $0.00048 | $0.00048 |
| Haiku 4.5 | $0.00024 | $0.00024 |
Grade A, and why
sandbox-cargo 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
Cargo stays in the sandbox
enableSharedBuildCache remaps Cargo dirs. It does not cover sccache.
~/.cargo/config.toml sets rustc-wrapper = "sccache". sccache is a
daemon (AF_UNIX / 127.0.0.1). Seatbelt denies both. That is
sccache: error: Operation not permitted.
.cargo/sccache-wrapper skips sccache when CURSOR_SANDBOX is set.
.cargo/config.toml overrides the home wrapper. Do not pin
target-dir / build-dir. That fights the shared Cargo cache.
Do not request all or disable the sandbox because cargo /
clippy / rustc failed. Do not retry as RUSTC_WRAPPER=. Restore
the wrapper if it is missing.
all is only for work that truly needs unrestricted filesystem or
network. A compile or unit test is not that.
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 First seen · 23 lines · 239 tokens per session scan A 36a7264935a6
sandbox-cargo is a cursor rule published in the GitHub repository zifeo/lade (135 stars, last pushed 4d ago), licensed MPL-2.0. It adds 239 tokens to every session, about $0.0010 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-09-06.
Other cursor rules, from other repositories
rust-module-refactor
Use when splitting Rust modules, moving tests, tightening visibility, or preserving facades during refactors.
rust-architect
PoolAI — Rust Architect workflow: runtime stack, MSYS2, target/ disk, pre-push checks, docs sync.
table-of-contents-standard
Standard section ordering and TOC format for Verus source files.
arc-deref-pattern
When implementing parallel (Mt) algorithms in Verus, do NOT assume.
wrap-vs-specify
When to use externaltypespecification vs wrapper struct for Verus specs.
core
Core STT/TTS abstraction layer documentation.