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/ccplugins/awesome-claude-code-plugins/remembergit clone --depth 1 https://github.com/ccplugins/awesome-claude-code-pluginsWrote 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/commands/ccplugins/awesome-claude-code-plugins/remember)<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>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 | $0.00008 | $0.00803 |
| Opus 5 | $0.00004 | $0.00402 |
| Sonnet 5 | $0.00002 | $0.00161 |
| Haiku 4.5 | $0.00001 | $0.00080 |
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.
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:
-
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
-
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
- Technology names:
-
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
-
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
-
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
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.
- yesterday First seen · 111 lines · 8 tokens per session scan A b023a4acb48f
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.
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.
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.
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.
pr-review
Reviews pull request changes to provide feedback, check for issues, and suggest improvements before merging into the main codebase.
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.
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.