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/sruja-ai/srujaWrote 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/sruja-ai/sruja/wasm-constraints)<a href="https://agentmods.dev/rules/sruja-ai/sruja/wasm-constraints"><img src="https://agentmods.dev/badge/rules/sruja-ai/sruja/wasm-constraints.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.1 | $0.00321 | $0.00321 |
| Opus 5 | $0.00161 | $0.00161 |
| Sonnet 5 | $0.00064 | $0.00064 |
| Haiku 4.5 | $0.00032 | $0.00032 |
Grade A, and why
wasm-constraints 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 7d 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
WASM Constraints
WASM-only crate constraints. Violations here break browser/Node builds.
Scopes
crates/sruja-wasm/**/*.rs
Rules
- No native-only APIs: Never use
std::fs,std::net,std::process, threads, or blocking I/O. Usewasm_bindgenabstractions. - No
println!: Useweb_sys::console::log_1orwasm_bindgen::JsValuefor logging. - No
std::time::Instant: Usejs_sys::Date::now()orweb_sys::Performancefor timing. - No
anyhow: Usewasm_bindgen::JsErroror custom error types that implementInto<JsValue>. - Serialize all boundaries: All data crossing the WASM/JS boundary must implement
serde::Serialize+serde::Deserialize. - Feature-gate native code: If a function needs both native and WASM paths, use
#[cfg(target_arch = "wasm32")]/#[cfg(not(target_arch = "wasm32"))]. - Keep exports minimal: Only expose functions intended for JS consumption via
#[wasm_bindgen].
Verification
After modifying WASM crates, run:
just wasm-nodejs # build for Node
just test-wasm # run wasm-pack tests
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.
- 7d ago First seen · 25 lines · 321 tokens per session scan A 6f60df5e79a9
wasm-constraints is a cursor rule published in the GitHub repository sruja-ai/sruja (23 stars, last pushed 7d ago), licensed Apache-2.0. It adds 321 tokens to every session, about $0.0016 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 cursor rules, from other repositories
rust-development
Rust development guidelines — ownership, borrowing, lifetimes, error handling, performance, concurrency, async, and testing patterns. Applied when working with Rust code.
rust-cli-conventions
Conventions for the CLI/TUI, provider abstraction, tool safety, and agent loop.
rust-native-architecture
Enforces native-first architecture and crate boundary rules for the nca workspace.
cargo-target-cache
Reuse src-tauri/target for cargo test; never isolate to an empty /tmp dir.
rust-architect
PoolAI — Rust Architect workflow: runtime stack, MSYS2, target/ disk, pre-push checks, docs sync.
rust-pro-auto
You are a Rust expert specializing in safe, performant systems programming.