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 skills/42u/laqrumcode/laqrumcode-forgetnpx skills add 42U/laqrumcode --skill laqrumcode-forgetgit clone --depth 1 https://github.com/42U/laqrumcodeWhat 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.00060 | $0.00467 |
| Opus 5 | $0.00030 | $0.00234 |
| Sonnet 5 | $0.00012 | $0.00093 |
| Haiku 4.5 | $0.00006 | $0.00047 |
Grade A, and why
laqrumcode-forget 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
laqrumcode forget (reversible)
Soft-forget content so it stops surfacing in retrieval. Honors the D4 founder
rule — nothing is deleted; matching rows are soft-deactivated with an audit
annotation (archive_reason='forget:…') and can be fully reactivated.
Usage
node scripts/forget.mjs --query "api key" # preview (DRY RUN)
node scripts/forget.mjs --query "api key" --commit # apply
node scripts/forget.mjs --before 2026-01-01 --commit # forget content older than a date
node scripts/forget.mjs --undo --commit # reactivate everything forgotten by this tool
Behavior
- DRY RUN by default — prints what would be forgotten (with samples); pass
--committo apply. - memory →
status='archived'; concept →superseded_atset — both witharchive_reason='forget:…'. The retrieval pipeline already excludes these, so they stop surfacing immediately, with no change to the hot retrieval path. - Reversible:
--undo --commitreactivates everything this tool forgot. - Nothing is DELETEd — rows survive for forensic recovery (D4).
Scope (v1)
- Selectors:
--query(case-insensitive substring) and--before(ISO date). - Tables:
memory+concept(the content tables whose retrieval candidate query already filters the deactivation flag). - Planned follow-ups:
--project/--session(edge-scoped) and never-remember redaction at ingestion (privacy.json). - Env:
SURREAL_URL/USER/PASS/NS/DB(same defaults as backup).
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 · 60 tokens per session scan A 038079f63340
laqrumcode-forget is a skill published in the GitHub repository 42U/laqrumcode (11 stars, last pushed 16d ago), licensed MIT. It adds 60 tokens to every session and 467 once invoked, about $0.0003 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…