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 mhmdreza-rafiei/agent-tools --skill remembergit clone --depth 1 https://github.com/mhmdreza-rafiei/agent-toolsWrote 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/mhmdreza-rafiei/agent-tools/remember)<a href="https://agentmods.dev/skills/mhmdreza-rafiei/agent-tools/remember"><img src="https://agentmods.dev/badge/skills/mhmdreza-rafiei/agent-tools/remember/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/mhmdreza-rafiei/agent-tools/remember"><img src="https://agentmods.dev/badge/skills/mhmdreza-rafiei/agent-tools/remember.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.00105 | $0.00855 |
| Opus 5.5 | $0.00042 | $0.00342 |
| Sonnet 5.5 | $0.00021 | $0.00171 |
| Haiku 4.5 | $0.00011 | $0.00085 |
Grade A, and why
remember 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 1mo 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI has no memory between sessions. Every new session starts blank. This skill fixes that. Save at the end, restore at the start — done consistently, nothing gets lost.
Memory lives in the context system: the canonical session state is context/memory/progress.md. /run-team owns team.md and /imprint owns ui-registry.md — read those on restore, never write them here.
Automation mode (default)
In automated/team flows, /remember save just saves — overwriting progress.md is its job, so don't prompt for the overwrite. The overwrite confirmation below is for interactive use. /remember restore still summarises what it restored (reality may have moved), but in automation it can proceed once summarised.
Security boundary
Never persist secrets. If a sensitive value appears (API keys, tokens, passwords, private keys, cookies, connection strings, webhook secrets, or any credential-like string), do not copy it to progress.md. Store a redacted placeholder (e.g. [REDACTED_API_KEY]). If unsure, treat it as sensitive and omit it. Run a final pass before writing to ensure nothing sensitive slipped in.
Invoke
/remember save (end of session) · /remember restore (start of session). Bare /remember → ask which, unless context makes it obvious.
Save
Capture only what a developer needs to continue cold — the essential state, not a transcript:
- Current state — what works, what's partial, what's broken.
- What was built — specific files/components/features this session (be precise).
- Decisions made — choices future work depends on (and fold durable ones into
architecture.md/plan.md). - Problems solved — so they aren't solved twice.
- Next session starts with — the very next action, specific.
- Open questions — anything unresolved.
Skip: implementation details visible in code, decisions already in the context files, and anything inferable from the codebase.
Write to context/memory/progress.md (if no context/, suggest /groundwork; else fall back to root memory.md). Interactive overwrite check (skipped in automation):
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.
- 1mo ago First seen · 67 lines · 105 tokens per session scan A 028aa563c991
remember is a skill published in the GitHub repository mhmdreza-rafiei/agent-tools (5 stars, last pushed 15d ago), licensed MIT. It adds 105 tokens to every session and 855 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
knowledge-ingest
Ingest documents, articles, conversations, or supplied text into Knowledge with retained originals, sourced claims, entity updates, source notes, and cross-links; also learn durable lessons from a set of conversations, transcripts, or past sessions (/learn), including the Learn from conversations and Learn from Memory…
mem0-oss-to-platform
Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…
forget
Remove a personal fact, preference, relationship detail, topic, or prior event from Muse's active memory and stop existing copies or automations from bringing it back. Use for explicit requests such as 'forget that', 'don't remember this about me', or 'remove that from your memory'. Do not use when 'forget it' merely…
Cortex
LifeOS memory, prior-session recall, and learning capture. USE WHEN capture this learning, document this learning, what did we learn recently, recent learnings, cortex, knowledge, knowledge base, search knowledge, what do we know about, archive, harvest, knowledge status, develop note, add to knowledge, add a people…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…