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/briangmilnes/APAS-VERUSWrote 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/briangmilnes/apas-verus/source-layout)<a href="https://agentmods.dev/rules/briangmilnes/apas-verus/source-layout"><img src="https://agentmods.dev/badge/rules/briangmilnes/apas-verus/source-layout/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/briangmilnes/apas-verus/source-layout"><img src="https://agentmods.dev/badge/rules/briangmilnes/apas-verus/source-layout.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.00060 | $0.00060 |
| Opus 5 | $0.00030 | $0.00030 |
| Sonnet 5 | $0.00012 | $0.00012 |
| Haiku 4.5 | $0.00006 | $0.00006 |
Grade A, and why
source-layout 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.
What it actually says
Rust Source Layout
- Source files go in
src/ - Test files go in
tests/ - Proof time tests go in
rust_verify_test/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.
- 5d ago First seen · 12 lines · 60 tokens per session scan A 3a95c9ace841
source-layout is a cursor rule published in the GitHub repository briangmilnes/APAS-VERUS (10 stars, last pushed 1mo ago), licensed MIT. It adds 60 tokens to every session, about $0.0003 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-09-03.
Other cursor rules, from other repositories
testing
Testing guidelines and patterns for skia-rs.
rust-quality
Rust engine quality gate — fmt, check, clippy, test, audit.
n-rust
A set of rules for Rust projects, covering code formatting, lint checks, continuous integration (automated checks run on code changes), and test coverage. It also sets requirements for documenting public Rust code.
core_test_isolation
A testing rule for Tauri applications that use an LLM, such as an agent, tool-calling system, or chat. Tauri is a framework for desktop apps, and the rule keeps agent logic in a separate Rust workspace package from the app shell.
cargo_mutants_config
A configuration rule for `cargo-mutants`, a Rust tool that checks tests by making small code changes and seeing whether tests catch them.
testing
Cursor rule "testing" from tyrchen/cursor-rust-rules, covering 🧪 rust testing standards, 🔍 testing strategy selection, 🏗️ cargo test organization, project structure for testing and unit test configuration.