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/threaded-test-timeout)<a href="https://agentmods.dev/rules/briangmilnes/apas-verus/threaded-test-timeout"><img src="https://agentmods.dev/badge/rules/briangmilnes/apas-verus/threaded-test-timeout/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/threaded-test-timeout"><img src="https://agentmods.dev/badge/rules/briangmilnes/apas-verus/threaded-test-timeout.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.00123 | $0.00123 |
| Opus 5 | $0.00062 | $0.00062 |
| Sonnet 5 | $0.00025 | $0.00025 |
| Haiku 4.5 | $0.00012 | $0.00012 |
Grade A, and why
threaded-test-timeout 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
Threaded Test Timeout
When creating or modifying a test that uses threads (std::thread, spawn, Pool, etc.):
- Wrap the test with a timeout to prevent hangs from deadlocks
- Use
timeoutcommand when running:timeout 60 cargo nextest run --test test_name - Or use a runtime timeout inside the test itself
Threaded tests can deadlock. A timeout ensures CI doesn't hang forever.
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 · 16 lines · 123 tokens per session scan A 0700f2540c58
threaded-test-timeout is a cursor rule published in the GitHub repository briangmilnes/APAS-VERUS (10 stars, last pushed 1mo ago), licensed MIT. It adds 123 tokens to every session, about $0.0006 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.
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.
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.
rust-testing
Rust Testing Best Practices.
test-quality-validation
Validates test quality and prevents testing theater anti-patterns in Rust test files.
mcp-server-attr-codegen-test
A set of Cursor coding rules for testing generated code from a Rust Model Context Protocol server attribute system. Code generation means producing source code automatically from declarations or annotations.