memory

A command for managing the project context file that a newly started coding worker reads for conventions and background information.

In plain words
What is it for?
It can enable, disable, select, or set the file used as the project's memory anchor.
Why use it?
It keeps important project guidance available across workers without replacing an existing context file.

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/thecolliery/coaltipple/memory
Clone the repo
git clone --depth 1 https://github.com/TheColliery/CoalTipple
Per session 26 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 172 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.00026 $0.00172
Opus 5 $0.00013 $0.00086
Sonnet 5 $0.00005 $0.00034
Haiku 4.5 $0.00003 $0.00017

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

Security

Grade A, and why

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

commands/memory.md · 12 lines

What it actually says

Manage CoalTipple's memory anchor — the project file a freshly-spawned worker reads for conventions and context beyond the bare task contract. Argument:

  • on — offer to create a memory file, choose an existing one, or skip.
  • off — disable the anchor and persist the choice (never re-ask).
  • set <file> — use the named file as the anchor.

Follow the Memory anchor procedure in the CoalTipple skill (SKILL.md); load and append to an existing anchor, never clobber it. Respond in the user's language. This is the /coaltipple memory action exposed as a discoverable command.

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 · 12 lines · 26 tokens per session scan A f2265b778753

Subscribe to this mod's changes

memory is a command published in the GitHub repository TheColliery/CoalTipple (6 stars, last pushed 2d ago), licensed Apache-2.0. It adds 26 tokens to every session and 172 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.