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 commands/scottrbk/forgetful/memory-listgit clone --depth 1 https://github.com/ScottRBK/forgetfulWhat 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.00006 | $0.00340 |
| Opus 5 | $0.00003 | $0.00170 |
| Sonnet 5 | $0.00001 | $0.00068 |
| Haiku 4.5 | $0.00001 | $0.00034 |
Grade A, and why
memory-list 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 3d 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
List Recent Memories
Show the most recently created memories from Forgetful.
Your Task
Retrieve recent memories using execute_forgetful_tool("get_recent_memories", {...}).
Arguments: $ARGUMENTS
Parameters
Parse the arguments for:
- Number: If user specifies a count (e.g., "10", "last 5"), use that as
limit - Project: If user mentions a project name, first list projects to get the ID, then filter
Default: {"limit": 10}
Response Format
Present memories in a clean, scannable format:
Recent Memories (showing X of Y):
1. [Title] (Importance: X, Created: date)
Tags: [tags]
2. [Title] (Importance: X, Created: date)
Tags: [tags]
...
Optional Enhancements
If the user asks for more detail on any memory, use get_memory to retrieve full content.
If filtering by project and no project_id provided, first call:
execute_forgetful_tool("list_projects", {})
Then let the user select or infer from context.
Examples
Basic usage:
/memory-list
Returns last 10 memories across all projects.
With count:
/memory-list 5
Returns last 5 memories.
With project filter:
/memory-list forgetful project
Lists projects, finds "forgetful" project ID, returns recent memories for that project.
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.
- 3d ago First seen · 67 lines · 6 tokens per session scan A dbd34eccf479
memory-list is a command published in the GitHub repository ScottRBK/forgetful (296 stars, last pushed 7d ago), licensed MIT. It adds 6 tokens to every session and 340 once invoked, about $0.0000 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 commands, from other repositories
prd-review
Review the active PRD with Codex and stream normalized findings to JSONL.
issue-amend
Re-snapshot the active issue's scope from the spec, clear verified and reviewed receipts, and record the change as a permanent amendment.
release
Prepare a release by updating docs and bumping the version.
everme-help
Print a concise EverMe plugin status + reference card.
q-research
Read the research-mode skill's SKILL.md for the full ruleset before proceeding. Follow all constraints, the source lookup cascade, the token budget, and the "what counts as cited" rules exactly.
recall
Recall relevant EverMe memories from past sessions and use them as context for the current task.