remember

A command for saving inline text as a named memory in a Quarry knowledge base.

In plain words
What is it for?
It helps store provided text under a chosen name for future knowledge-base use.
Why use it?
It keeps useful information available for later instead of leaving it only in the current conversation.

Command

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/punt-labs/quarry/remember
Clone the repo
git clone --depth 1 https://github.com/punt-labs/quarry
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 150 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 89% copy Near-identical to another mod 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.00150
Opus 5 $0.00004 $0.00075
Sonnet 5 $0.00002 $0.00030
Haiku 4.5 $0.00001 $0.00015

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

Origin

This is a copy

89% identical to remember-dev — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

plugin/commands/remember.md · 23 lines

What it actually says

Input

Arguments: $ARGUMENTS

The arguments are the name for this memory, not a filename.

Task

Ask the user for the content to remember (or accept it from the conversation context if already provided).

Call mcp__plugin_quarry_quarry__remember with:

  • content set to the text content
  • document_name set to the arguments (the memory's name)

The result is already formatted by a PostToolUse hook and displayed above. Do not repeat or reformat the data. Do not send any text after the tool call.

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 · 23 lines · 8 tokens per session scan A 363755d28a3b

Subscribe to this mod's changes

remember is a command published in the GitHub repository punt-labs/quarry (3 stars, last pushed 2d ago), licensed MIT. It adds 8 tokens to every session and 150 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to remember-dev, differing in 2 lines, and is treated as a copy.