cog: Command for Claude Code

.claude/commands/history.md

history is a command for Claude Code from marciopuga/cog. It costs 44 tokens per session (610 once invoked), scanned A, original, MIT.

A command for searching an AI agent's stored notes across conversations, people, topics, and tasks. It combines results from several memory files to reconstruct what happened over time.

In plain words
What is it for?
Use it to find an earlier conversation, trace the history of a decision, or recall related observations and unfinished tasks.
Why use it?
It helps answer questions about past discussions when the information is spread across many files.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is marciopuga/cog's own configuration. It tells Claude Code how to work on cog itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything cog configures →

Reuse

Borrowing it

Nothing to install: this file belongs to marciopuga/cog. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/marciopuga/cog/main/.claude/commands/history.md
Clone the repo
git clone --depth 1 https://github.com/marciopuga/cog

Made for: Claude Code.

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

agentmods badge for history

README.md
[![agentmods](https://agentmods.dev/badge/commands/marciopuga/cog/history/github.svg)](https://agentmods.dev/commands/marciopuga/cog/history)
Your own site
<a href="https://agentmods.dev/commands/marciopuga/cog/history"><img src="https://agentmods.dev/badge/commands/marciopuga/cog/history/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.

agentmods 80×15 button for history

Your own site · 80×15
<a href="https://agentmods.dev/commands/marciopuga/cog/history"><img src="https://agentmods.dev/badge/commands/marciopuga/cog/history.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 44 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 610 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00044 $0.00610
Opus 5.5 $0.00018 $0.00244
Sonnet 5.5 $0.00009 $0.00122
Haiku 4.5 $0.00004 $0.00061

Measured 2mo ago against content hash 2ec86d66bf1d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

history 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 2mo 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.

.claude/commands/history.md · 65 lines

How it starts

The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Use this skill for deep memory search and recall. Trigger if the user says "what did I say about...", "when did we discuss...", "find that conversation about...", "history of...", or asks about past information that needs multi-file search. For simple date/keyword lookups, a quick Grep suffices — this skill is for when you need to piece together a narrative from multiple entries.

Domain

Memory recall — recursive search across all memory files, cross-referencing observations, entities, and action items.

Memory Path

All files under the resolved memory path: $COG_HOME/memory/ if COG_HOME is set, otherwise ~/cog/memory/. All memory/... references below are relative to this root.

Memory Files

Read on activation:

  • memory/hot-memory.md (for context on what's currently relevant)

Search across:

  • All observations.md files (personal, work domains, cog-meta)
  • All entities.md files
  • All action-items.md files
  • All hot-memory.md files
  • memory/glacier/ (via index.md for targeted retrieval)

Process

Pass 1: Locate

  • Extract keywords from the user's query (names, topics, dates, phrases)
  • If the query names a domain (or memory/domains.yml triggers match), grep inside that domain first; fall back to the whole memory root only when the domain is unknown
  • Grep for each keyword
  • Note which files matched and how many hits
  • If >10 files match, narrow by domain or add query terms
  • If 0 matches, try synonyms or related terms
  • Check memory/glacier/index.md for archived data matching the query

Pass 2: Extract

  • Read the top 3-5 most relevant files (by hit density and recency)
  • Extract the specific passages that match the query
  • Track the timeline: when did the topic first come up? How did it evolve?

Pass 3: Synthesize

  • Combine extracted passages into a coherent answer
  • Present findings chronologically with dates
  • If something seems incomplete, flag it:

    "Found references to X in observations but no entity entry — want me to create one?"

Read the full file on GitHub · 65 lines

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. 2mo ago Changed · +1 lines 2ec86d66bf1d
  2. 2mo ago First seen · 64 lines · 44 tokens per session scan A 8302b64e6ec1

Subscribe to this mod's changes

history is a command published in the GitHub repository marciopuga/cog (377 stars, last pushed 2mo ago), licensed MIT. It adds 44 tokens to every session and 610 once invoked, about $0.0002 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-30.

Related

history compared with commands from other repositories

history next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
historymarciopuga/cogCommand3772mo agoMITA44Claude Code
minutes-ideassilverstein/minutesCommand1.6kyesterdayMITA48Claude Code, OpenCode
learnReflexioAI/claude-smartCommand7913d agoApache-2.0A14Claude Code
memory-storeverygoodplugins/mcp-automemCommand66todayMITA10Claude Code
analyze-contextRohiRIK/OpenLtmCommand298d agoMITA39Claude Code
cc-memoryTheLobbi/claudeCommand217d agoMITA0Claude Code
lians-recallLians-ai/LiansCommand174d agoApache-2.0A19Claude Code