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 skills add ScottRBK/forgetful --skill forgetful-context-gathergit clone --depth 1 https://github.com/ScottRBK/forgetfulWrote 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/skills/scottrbk/forgetful/forgetful-context-gather)<a href="https://agentmods.dev/skills/scottrbk/forgetful/forgetful-context-gather"><img src="https://agentmods.dev/badge/skills/scottrbk/forgetful/forgetful-context-gather/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/skills/scottrbk/forgetful/forgetful-context-gather"><img src="https://agentmods.dev/badge/skills/scottrbk/forgetful/forgetful-context-gather.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00063 | $0.00959 |
| Opus 5 | $0.00032 | $0.00479 |
| Sonnet 5 | $0.00013 | $0.00192 |
| Haiku 4.5 | $0.00006 | $0.00096 |
Grade A, and why
forgetful-context-gather 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gathering context before work
A single query answers a question; a context gather prepares a task. The output is a pack the work can lean on, with every claim cited by memory ID and every dry angle stated — silence is never ambiguous.
Invoking operations
Operations are named by registry name (query_memory, get_document, ...). Invoke via
whichever surface this agent has:
- MCP:
execute_forgetful_tool(tool_name="query_memory", arguments={...}) - CLI:
forgetful call query_memory --args '{"query": "..."}' --json
Get any operation's schema at runtime: how_to_use_forgetful_tool (MCP) or
forgetful tools info <operation> (CLI) — schemas are deliberately not repeated here.
Delegating this workflow to a subagent: hand it the CLI flavor — Bash travels into
subagents, MCP tool access does not. Run MCP-flavored gathers in the main conversation.
Step 1 — Derive the query angles
From the task description, write 3–5 distinct angles: the feature area, the technology or library, exact error text or identifiers, the architectural layer, adjacent domains that share patterns. One angle is a spot-check; several are coverage.
Done when: the angles are listed before any query runs.
Step 2 — Recall per angle
query_memory per angle — query and query_context are both required, and
query_context should carry the task's intent (per forgetful-recall: reads cross-project
by default, identifiers verbatim, truncated handled). Skills referenced by name in this
skill resolve via search_skills → export_skill when not already available. Track which
angles hit and which came up dry.
Done when: every angle has run and its outcome is recorded.
Step 3 — Explore around the strongest hits
Where hits reference entities or cluster into a topic, walk the graph (per
forgetful-explore, medium depth): expand the memories, discover the entities, harvest
what is attached to them.
Done when: the strongest hits have their neighbourhood mapped, not just their own text.
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.
- 9d ago First seen · 95 lines · 63 tokens per session scan A 78d07fe5c3c0
forgetful-context-gather is a skill published in the GitHub repository ScottRBK/forgetful (299 stars, last pushed 7d ago), licensed MIT. It adds 63 tokens to every session and 959 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
synap
Add persistent, structured long-term memory to AI agents using Maximem Synap. Use this skill whenever the user is building, debugging, or evaluating an AI agent and mentions any of: "memory", "long-term memory", "persistent memory", "agent memory", "remember across sessions", "context window", "agent forgets", "user…
project-memory
Generate a project-specific context file from a brief so an AI assistant remembers your editorial constraints, voice, audience, and quality bar across sessions.
synap
Add persistent, structured long-term memory to AI agents using Maximem Synap. Use this skill whenever the user is building, debugging, or evaluating an AI agent and mentions any of: "memory", "long-term memory", "persistent memory", "agent memory", "remember across sessions", "context window", "agent forgets", "user…
memory-bank
Maintain and update project memory-bank files for persistent context across Claude Code sessions. Use when starting a new session, completing features, making architectural changes, or when context needs to be preserved. Triggers on: memory bank, project context, session start, context update, CLAUDE.md, project…
recall
Fan-out search across all memory sources when context is unclear or vaguely referenced. Triggers on: 'from earlier', 'remember when', 'what we discussed', 'that thing with', 'the conversation about', 'did we ever', 'what happened with', 'you mentioned', 'we talked about', 'earlier today', 'last session', 'the other…
planning-with-files
Manus-style persistent markdown planning - use filesystem as working memory with taskplan.md, findings.md, and progress.md for complex multi-step tasks that survive context resets.