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/beardfaceguy/daimonosWrote 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/beardfaceguy/daimonos/bounded-collections)<a href="https://agentmods.dev/rules/beardfaceguy/daimonos/bounded-collections"><img src="https://agentmods.dev/badge/rules/beardfaceguy/daimonos/bounded-collections/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/beardfaceguy/daimonos/bounded-collections"><img src="https://agentmods.dev/badge/rules/beardfaceguy/daimonos/bounded-collections.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.00000 | $0.00316 |
| Opus 5.5 | $0.00000 | $0.00126 |
| Sonnet 5.5 | $0.00000 | $0.00063 |
| Haiku 4.5 | $0.00000 | $0.00032 |
Grade A, and why
bounded-collections 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 2mo 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
Bounded Collections in Long-Lived State
Every HashMap, BTreeMap, or Vec stored in a struct that lives for the
duration of a session (e.g. Session, plugin caches, pipeline state) must
have a maximum size with an eviction strategy.
What went wrong
Four separate caches (read_cache, exec_usage, decl_cache,
pipeline_cache.entries) were implemented as plain HashMap::insert() with
no size check. Over a long session, each could grow without bound.
Rule
- When adding a collection to a long-lived struct, decide the max size
at design time and make it configurable (via
Config) where possible. - Before every
.insert(), checklen() >= maxand evict. - Prefer the simplest eviction that fits: arbitrary eviction (
.keys().next()) for caches, least-used eviction for frequency counters.
Example
// BAD: unbounded insert
self.cache.insert(key, value);
// GOOD: bounded insert with eviction
if self.cache.len() >= self.cfg.max_cache_entries {
let evict = self.cache.keys().next().cloned();
if let Some(k) = evict {
self.cache.remove(&k);
}
}
self.cache.insert(key, value);
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.
- 2mo ago First seen · 42 lines · 0 tokens per session scan A 4677996b2a13
bounded-collections is a cursor rule published in the GitHub repository beardfaceguy/daimonos (3 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 316 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
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).
control-plane-descriptors
Control plane descriptor and instance implementation patterns.