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/beardfaceguy/daimonos/no-thread-spawn-in-callbacksgit clone --depth 1 https://github.com/beardfaceguy/daimonosWhat 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.00283 |
| Opus 5 | $0.00000 | $0.00142 |
| Sonnet 5 | $0.00000 | $0.00057 |
| Haiku 4.5 | $0.00000 | $0.00028 |
Grade A, and why
no-thread-spawn-in-callbacks 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
No Thread Spawning in High-Frequency Callbacks
Never use std::thread::spawn inside a callback that fires on every
filesystem event, network packet, or timer tick.
What went wrong
The pipeline cache's notify watcher callback spawned a new OS thread on
every filesystem modify/create/remove event, just to set a boolean flag.
Under heavy churn, this created hundreds of short-lived threads — an
unnecessary resource drain.
Rule
- If you only need to flip a flag, use
AtomicBoolwithOrdering::Relaxed. - If you need to send structured data, use a bounded channel
(
std::sync::mpscorcrossbeam). - If you absolutely need async from a sync callback, use
tokio::runtime::Handle::try_current()withspawn— notstd::thread::spawn+block_on.
Example
// BAD: thread per event
std::thread::spawn(move || {
rt.block_on(async { state.write().await.dirty = true; });
});
// GOOD: lock-free atomic flag
dirty_flag.store(true, Ordering::Relaxed);
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 · 39 lines · 0 tokens per session scan A 81c51d578421
no-thread-spawn-in-callbacks is a cursor rule published in the GitHub repository beardfaceguy/daimonos (2 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 283 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
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.