remember

remember is a command for coding agents from ccplugins/awesome-claude-code-plugins. It costs 8 tokens per session (803 once invoked), scanned A, original, Apache-2.0.

A command that saves a summary of the current coding session to persistent context memory, with an optional note or tag.

In plain words
What is it for?
Use it to record completed work, important implementation details, or OAuth and authentication decisions for later reference.
Why use it?
It preserves decisions, solved problems, technologies, and outcomes so the work can be found after the session ends.

Command

Part of the context-memory plugin — 1 skill, 1 command shipped together

Install

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.

agentmods
npx agentmods add commands/ccplugins/awesome-claude-code-plugins/remember
Clone the repo
git clone --depth 1 https://github.com/ccplugins/awesome-claude-code-plugins

Or install context-memory, the plugin that ships this one along with the rest of its 1 skill, 1 command.

Wrote 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.

agentmods badge for remember

README.md
[![agentmods](https://agentmods.dev/badge/commands/ccplugins/awesome-claude-code-plugins/remember.svg)](https://agentmods.dev/commands/ccplugins/awesome-claude-code-plugins/remember)
Your own site
<a href="https://agentmods.dev/commands/ccplugins/awesome-claude-code-plugins/remember"><img src="https://agentmods.dev/badge/commands/ccplugins/awesome-claude-code-plugins/remember.svg" alt="Measured on agentmods" height="20"></a>
Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 803 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00008 $0.00803
Opus 5 $0.00004 $0.00402
Sonnet 5 $0.00002 $0.00161
Haiku 4.5 $0.00001 $0.00080

Measured yesterday against content hash b023a4acb48f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 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.

plugins/context-memory/commands/remember.md · 111 lines

How it starts

The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/remember Command

Save the current session to context memory with an optional annotation.

Usage

/remember [note]

Arguments:

  • note (optional): A personal annotation or tag to help find this session later

Examples

/remember
/remember "Fixed the auth bug with refresh tokens"
/remember "Important: OAuth2 implementation details"

Workflow

When the user runs /remember:

  1. Generate Session Summary

    Analyze the current conversation and create:

    • brief: A single sentence summarizing what was accomplished
    • detailed: 2-3 paragraphs with full context of what happened
    • key_decisions: List of important decisions made during the session
    • problems_solved: List of problems that were resolved
    • technologies: List of technologies, frameworks, or tools discussed
    • outcome: One of: success, partial, abandoned
  2. Extract Topics

    Identify 3-8 relevant topics from the conversation. Use lowercase, common terms like:

    • Technology names: react, python, sqlite
    • Concepts: authentication, debugging, refactoring
    • Domains: api, frontend, database
  3. Identify Key Code

    If significant code was written or discussed, extract important snippets with:

    • The code itself
    • The programming language
    • A brief description of what it does
    • The file path if applicable
  4. Extract Key Messages

    Select 5-15 important messages from the conversation that capture:

    • The initial request/problem statement
    • Key decisions and their reasoning
    • Solution descriptions
    • Important caveats or warnings
  5. Pipe JSON via Stdin and Save to Database

    Pipe JSON directly via --json - (stdin):

    python "~/.claude/skills/context-memory/scripts/db_save.py" --json - << 'ENDJSON'
    {
      "session_id": "<UNIQUE_ID>",
      "project_path": "<PROJECT_PATH>",
      "messages": [
        {"role": "user", "content": "The initial question or request"},
        {"role": "assistant", "content": "The response or solution"}
      ],
      "summary": {
        "brief": "One-line summary of what was accomplished",
        "detailed": "2-3 paragraphs with full context...",
        "key_decisions": ["Decision 1", "Decision 2"],
        "problems_solved": ["Problem 1", "Problem 2"],
        "technologies": ["python", "sqlite", "fts5"],
        "outcome": "success"
      },
      "topics": ["topic1", "topic2", "topic3"],
      "code_snippets": [
        {
          "code": "def example(): pass",
          "language": "python",
          "description": "What this code does",
          "file_path": "src/example.py"
        }
      ],
      "user_note": "User's note if provided, or null"
    }
    ENDJSON
    

Read the full file on GitHub · 111 lines

Changes

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.

  1. yesterday First seen · 111 lines · 8 tokens per session scan A b023a4acb48f

Subscribe to this mod's changes

remember is a command published in the GitHub repository ccplugins/awesome-claude-code-plugins (931 stars, last pushed 23d ago), licensed Apache-2.0. It adds 8 tokens to every session and 803 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-09-03.

Related

Other commands, from other repositories

create-pull-request

Provides comprehensive PR creation guidance with GitHub CLI, enforcing title conventions, following template structure, and offering concrete command examples with best practices.

xbim08/awesome-claude-code-plugins · 27 tokens

pr-issue-resolve

Follow these steps to analyze suggested changes (e.g., review comments, inline suggestions, or requested modifications) in a GitHub Pull Request (PR) and resolve them efficiently. The goal is to review, understand, plan fixes, apply changes, test, and update the PR while maintaining code quality and collaboration.

xbim08/awesome-claude-code-plugins · 14 tokens

openapi-expert

Use this agent when you need to update, synchronize, or validate the OpenAPI specification (openapi.yml) against the actual REST API implementation. This includes adding new endpoints, updating request/response schemas, fixing discrepancies between the spec and code, or ensuring complete API documentation coverage.

xbim08/awesome-claude-code-plugins · 61 tokens

pr-review

Reviews pull request changes to provide feedback, check for issues, and suggest improvements before merging into the main codebase.

xbim08/awesome-claude-code-plugins · 23 tokens

create-pr

Streamlines pull request creation by handling the entire workflow: creating a new branch, committing changes, formatting modified files with Biome, and submitting the PR.

xbim08/awesome-claude-code-plugins · 31 tokens

husky

Sets up and manages Husky Git hooks by configuring pre-commit hooks, establishing commit message standards, integrating with linting tools, and ensuring code quality on commits.

xbim08/awesome-claude-code-plugins · 33 tokens