remember

A user-triggered note-taking workflow for saving decisions, facts, procedures, or gotchas in an Obsidian vault. Obsidian is a note-taking app that stores notes as files.

In plain words
What is it for?
Use it to record architectural choices, workflow steps, objective facts, and unexpected limitations, with the project and date included.
Why use it?
It keeps important project knowledge from being lost in a chat or session. Each item becomes a structured note that can be found later.

Skill for Claude CodeCodex

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 skills/jl-cmd/claude-dev-env/remember
Any agent
npx skills add jl-cmd/claude-dev-env --skill remember
Clone the repo
git clone --depth 1 https://github.com/jl-cmd/claude-dev-env

Made for: Claude Code, Codex.

Per session 25 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 554 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.00025 $0.00554
Opus 5 $0.00013 $0.00277
Sonnet 5 $0.00005 $0.00111
Haiku 4.5 $0.00003 $0.00055

Measured 2d ago against content hash 1c2010e8797d, 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 2d 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.

packages/claude-dev-env/.agents/skills-archived/remember/SKILL.md · 64 lines

What it actually says

Remember

Save a structured decision, gotcha, or architectural choice to the Obsidian vault as an individual note in the decisions/ directory.

Instructions

  1. Parse the input. Extract the core decision, fact, or gotcha from $ARGUMENTS.

  2. Classify the type based on content:

    • decision -- a choice made between alternatives (e.g., "chose Groq over Gemini")
    • procedural -- a how-to or workflow step (e.g., "deploy requires manual cookie refresh first")
    • fact -- an objective piece of information (e.g., "YNAB API cannot overwrite split transactions")
    • gotcha -- a surprising behavior or trap (e.g., "Amazon blocks Cloud Run datacenter IPs")
  3. Infer the project name from conversation context (git remote, working directory, or topic).

  4. Generate a short title (3-7 words) that captures the essence.

  5. Write to vault via mcp__obsidian__write_note:

    Path: decisions/[Project] - [Short Title].md

    Frontmatter:

    name: [Short Title from step 4]
    description: [One-line summary of the decision/fact/gotcha -- concise enough for frontmatter search]
    type: [decision|procedural|fact|gotcha]
    project: [Project Name]
    date: [YYYY-MM-DD]
    status: Active
    tags: [relevant, tags]
    

    Body format depends on type:

    For decision:

    **Decision:** [One sentence stating what was decided]
    **Reasoning:** [Why this was chosen]
    **Alternatives considered:** [What was rejected and why]
    **Consequences:** [What this means going forward]
    

    For gotcha:

    **Gotcha:** [One sentence stating the surprising behavior]
    **Symptom:** [What you observe when you hit this]
    **Fix:** [How to work around or resolve it]
    

    For fact or procedural:

    [The fact or procedure, written clearly in 1-3 sentences with relevant context]
    
  6. Confirm what was saved and where (vault path).

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 2d ago First seen · 64 lines · 25 tokens per session scan A 1c2010e8797d

Subscribe to this mod's changes

remember is a skill published in the GitHub repository jl-cmd/claude-dev-env (6 stars, last pushed 2d ago), licensed MIT. It adds 25 tokens to every session and 554 once invoked, about $0.0001 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-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens