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/irskep/persistprocWrote 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/irskep/persistproc/200_logging_strategy)<a href="https://agentmods.dev/rules/irskep/persistproc/200_logging_strategy"><img src="https://agentmods.dev/badge/rules/irskep/persistproc/200_logging_strategy/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/irskep/persistproc/200_logging_strategy"><img src="https://agentmods.dev/badge/rules/irskep/persistproc/200_logging_strategy.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.00253 | $0.00253 |
| Opus 5.5 | $0.00101 | $0.00101 |
| Sonnet 5.5 | $0.00051 | $0.00051 |
| Haiku 4.5 | $0.00025 | $0.00025 |
Grade A, and why
200_logging_strategy 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
Logging in this project should be detailed, scoped, and extensive. Logs are the primary way to debug test runs, so they should make execution history obvious.
There should be an explicit log scope for command line output. Without -v or -vv, all other logging should be silenced from the command line.
Otherwise, each module and function should have its own log scope. Error, warn, info, and debug levels should be used appropriately.
Each invocation of persistproc should write a complete log with debug verbosity to data_dir/persistproc.run..log. This may require synchronizing across threads or using multiprocessing and a queue, since we're managing multiple processes potentially using threads, but we don't necessarily need to go that far until we know we need it.
The outcome is that after every failed test run, we'll have incredible detail to see exactly what happened and find an appropriate fix that doesn't involve setting arbitrary timeouts.
Prefer scoped log objects over the global logger.
Logging is already configured in logging_utils.py.
LOG FORMAT Debug logs should be machine-readable first, human-readable second. It should be easy to write test cases against these logs because the wording in English will not shift around.
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 · 21 lines · 253 tokens per session scan A 51e6753c75e1
200_logging_strategy is a cursor rule published in the GitHub repository irskep/persistproc (8 stars, last pushed 1y ago), licensed MIT. It adds 253 tokens to every session, about $0.0010 per session on Opus 5.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-08-31.
Other cursor rules, from other repositories
error-handling-and-validation
A code-quality guide for handling errors, invalid inputs, edge cases, preconditions, logging, and user-friendly error messages.
css-render-blocking-diagnosis
Cursor rule "css-render-blocking-diagnosis" from adobecom/da-express-milo, covering css render-blocking diagnosis & resolution, critical learning from 98 pagespeed achievement, primary diagnostic protocol, step 1: css blocking symptom recognition and step 2: css loading sequence audit.
modus-checkbox-value-inversion-react-short
Critical bug fix for ModusWcCheckbox value property inversion.
javascript-expert-performance
Profile first. Measure before and after. Never optimize without data.
kiss-ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
5-bug-finder
APPLY WHEN investigating a bug.