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/major7apps/pensyve/memory-informed-debuggit clone --depth 1 https://github.com/major7apps/pensyveWhat 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.00023 | $0.00798 |
| Opus 5 | $0.00012 | $0.00399 |
| Sonnet 5 | $0.00005 | $0.00160 |
| Haiku 4.5 | $0.00002 | $0.00080 |
Grade A, and why
memory-informed-debug 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- yesterday First seen · 69 lines · 23 tokens per session scan A dab5beed10a3
memory-informed-debug is a cursor rule published in the GitHub repository major7apps/pensyve (72 stars, last pushed 3d ago), with no licence file. It adds 23 tokens to every session and 798 once invoked, about $0.0001 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-08-30.
Other cursor rules, from other repositories
defensive-invariants
Defensive invariants — when a check may be deleted — Deleting a defensive check because a proof says it cannot fire is the most expensive class of mistake made in this codebase. Canonical file is .agents/rules/defensive-invariants.md.
module-state-ownership
Module-state ownership & caches built from hot-reloading settings — How mutable module-scope state is owned here, and what caching anything derived from settings() obliges. Canonical file is .agents/rules/module-state-ownership.md.
dev-principles
Follow the canonical rule (edit that file, never this shadow).
docs-style
README and docs style for llm-wiki-memory — install-first structure, plain-English jargon, vertical Mermaid with quoted labels, badge rules. Canonical file is .agents/rules/docs-style.md.
release-migrations-authoring
Authoring a release migration (llm-wiki-memory itself) — This rule governs developing llm-wiki-memory itself. Canonical file is .agents/rules/release-migrations-authoring.md.
run-tests-safely
Run the llm-wiki-memory test suite without filling /tmp — sweep stale lwm- workspaces, iterate on single files, run npm test once. Use when running or debugging tests in this repo.