test-full-lifecycle

A testing rule for resources such as processes, maps, and temporary files. It says tests should check not only that a resource is created and used, but also that it is removed afterward.

In plain words
What is it for?
Use it when testing background processes, temporary files, caches, file handles, or other resources with a start-and-end lifecycle.
Why use it?
Cleanup bugs can remain hidden when tests stop after the successful part of an operation. Repeating the operation also reveals resources that quietly accumulate.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/beardfaceguy/daimonos/test-full-lifecycle
Clone the repo
git clone --depth 1 https://github.com/beardfaceguy/daimonos

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 310 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00310
Opus 5 $0.00000 $0.00155
Sonnet 5 $0.00000 $0.00062
Haiku 4.5 $0.00000 $0.00031

Measured yesterday against content hash 28e3dab93a11, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

test-full-lifecycle 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 yesterday.

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.

.cursor/rules/test-full-lifecycle.mdc · 43 lines

What it actually says

Test the Full Resource Lifecycle

When writing tests for resource management, don't just test the happy path of creation and use. Test that resources are cleaned up afterward.

What went wrong

The original bg tests verified that bg() spawned a process and poll() returned results, but never checked that the process entry was removed from the map or that the temp log file was deleted. The bugs lived in untested teardown paths for months.

Rule

  1. After the "done" action (poll returns exit, kill succeeds, cache clears), assert the resource is gone: map is empty, file doesn't exist, count is zero.
  2. Write an accumulation test: run N operations in a loop, then verify the resource count is bounded (e.g. assert!(map.is_empty()) or assert!(map.len() <= MAX)).
  3. For disk resources, assert file non-existence with assert!(!path.exists()).

Example

// After polling a completed process:
assert!(!session.bg_processes.contains_key(&pid));
assert!(!log_path.exists());

// Accumulation test:
for _ in 0..10 {
    spawn_and_complete(&mut session).await;
}
assert!(session.bg_processes.is_empty());
Changes

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.

  1. yesterday First seen · 43 lines · 0 tokens per session scan A 28e3dab93a11

Subscribe to this mod's changes

test-full-lifecycle is a cursor rule published in the GitHub repository beardfaceguy/daimonos (2 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 310 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.