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 kopp0510/claude-dd --skill remembergit clone --depth 1 https://github.com/kopp0510/claude-ddWrote 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/kopp0510/claude-dd/remember)<a href="https://agentmods.dev/skills/kopp0510/claude-dd/remember"><img src="https://agentmods.dev/badge/skills/kopp0510/claude-dd/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/kopp0510/claude-dd/remember"><img src="https://agentmods.dev/badge/skills/kopp0510/claude-dd/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.00029 | $0.00951 |
| Opus 5.5 | $0.00012 | $0.00380 |
| Sonnet 5.5 | $0.00006 | $0.00190 |
| Haiku 4.5 | $0.00003 | $0.00095 |
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- remember — 92% identical, 31 lines differ
How it starts
The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/self-improving-agent:remember — Save Knowledge Explicitly
Writes an explicit entry to auto-memory when something is important enough that you don't want to rely on Claude noticing it automatically.
Usage
/self-improving-agent:remember <what to remember>
/self-improving-agent:remember "This project's CI requires Node 20 LTS — v22 breaks the build"
/self-improving-agent:remember "The /api/auth endpoint uses a custom JWT library, not passport"
/self-improving-agent:remember "Reza prefers explicit error handling over try-catch-all patterns"
When to Use
| Situation | Example |
|---|---|
| Hard-won debugging insight | "CORS errors on /api/upload are caused by the CDN, not the backend" |
| Project convention not in CLAUDE.md | "We use barrel exports in src/components/" |
| Tool-specific gotcha | "Jest needs --forceExit flag or it hangs on DB tests" |
| Architecture decision | "We chose Drizzle over Prisma for type-safe SQL" |
| Preference you want Claude to learn | "Don't add comments explaining obvious code" |
Workflow
Step 1: Parse the knowledge
Extract from the user's input:
- What: The concrete fact or pattern
- Why it matters: Context (if provided)
- Scope: Project-specific or global?
Step 2: Check for duplicates
# Claude Code replaces EVERY non-alphanumeric character in the resolved absolute cwd
# with a single "-" (dots, spaces and CJK included).
MEMORY_DIR="$HOME/.claude/projects/$(pwd -P | sed 's/[^a-zA-Z0-9]/-/g')/memory"
# Verify before writing — a wrong path loses the entry silently while still looking saved.
# Under LC_ALL=C sed goes per byte, so glob as a fallback:
# [ -d "$MEMORY_DIR" ] || ls -d ~/.claude/projects/*"$(basename "$PWD" | sed 's/[^a-zA-Z0-9]/-/g')"*
grep -ni "<keywords>" "$MEMORY_DIR/MEMORY.md" 2>/dev/null
If a similar entry exists:
- Show it to the user
- Ask: "Update the existing entry or add a new one?"
Step 3: Write to MEMORY.md
Append to the end of MEMORY.md:
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 Changed · +5 lines e02d25f209ef
- 1mo ago First seen · 100 lines · 29 tokens per session scan A d986e3b25621
remember is a skill published in the GitHub repository kopp0510/claude-dd (12 stars, last pushed yesterday), licensed MIT. It adds 29 tokens to every session and 951 once invoked, about $0.0001 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-08-31.
Other skills, from other repositories
remember
Review the current conversation and capture valuable knowledge — best practices, coding conventions, architecture decisions, workflows, and user feedback — into persistent memory (AGENTS.md) or reusable skills. Use when the user says: (1) remember this, (2) save what we learned, (3) update memory, (4) capture…
md-audit
Read-only code quality audit — scan the current working directory for common issues (bugs, dead code, security hotspots, missing error handling) and return a prioritised findings report. No files are edited. Use when asked to "audit the code", "quick audit", "find issues", "code scan", or "what's wrong with this…
impl-validator
Independently check whether an implementation matches its stated goal and return PASS/WARN/FAIL with actionable issues. Use for second-opinion validation of an implementation or generated output.
memory-to-skill
Turn workflows from your MemSearch memory into reusable skills. Use when the user asks to make/create/extract/distill a skill from what they just did or from past work, review skill candidates, install a distilled skill, or 'turn this into a skill'. Manages MemSearch procedural-memory candidates under…
mindos
MindOS: local knowledge assistant & shared KB. Keeps decisions, notes, SOPs, debugging lessons, research findings, preferences across sessions/agents. Core: save notes, search KB, organize files, run workflows, review, append CSV, hand off context, distill lessons. NOT for app source or paths outside KB. Triggers…
agents-md-improver
Audit and improve project-rules files (AGENTS.md, CLAUDE.md, .agents/instructions, local overrides) so the agent keeps accurate project context. Use when the user asks to check, audit, review, update, improve, or fix their AGENTS.md or CLAUDE.md, mentions "project rules maintenance" or "agent context optimization", or…