What is temporal-query?

A tool for answering questions about how stored memories changed over time. It distinguishes what the memory store contained at a past point from what was true in the outside world.

Use it for questions such as “what did I believe then?”, “when did this change?”, “what replaced the old memory?”, or “what did the store contain as of a certain date?”

Normal searches show only current memories, so they cannot explain older beliefs, replacements, or deletions. This provides the recorded history and warns that its dates describe when memories were stored.

temporal-query — Skill for Claude Code by n24q02m

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.

Any agent

npx skills add n24q02m/mnemo-mcp --skill temporal-query

Clone the repo

git clone --depth 1 https://github.com/n24q02m/mnemo-mcp

Made for: Claude Code.

Or install mnemo-mcp, the plugin that ships this one along with the rest of its 6 skills, 2 hooks, 1 MCP server.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/n24q02m/mnemo-mcp/temporal-query.svg)](https://agentmods.dev/skills/n24q02m/mnemo-mcp/temporal-query)

Your own site

<a href="https://agentmods.dev/skills/n24q02m/mnemo-mcp/temporal-query"><img src="https://agentmods.dev/badge/skills/n24q02m/mnemo-mcp/temporal-query.svg" alt="Measured on agentmods" height="20"></a>

Per session 77 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,707 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. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

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.

Model	Per session	Once invoked
Fable 5.1	$0.00077	$0.01707
Opus 5	$0.00039	$0.00853
Sonnet 5	$0.00015	$0.00341
Haiku 4.5	$0.00008	$0.00171

Measured 8d ago against content hash 99dbeacf9b68, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

temporal-query 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 8d 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

Copies of this mod

1 near-identical copy found in the catalogue:

temporal-query — 100% identical, 0 lines differ

skills/temporal-query/SKILL.md · 138 lines

How it starts

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

Temporal Query

Point-in-time and version-chain lookups over the bitemporal columns (valid_from, valid_to, superseded_by) that mem_003_temporal added to memories. Ordinary search cannot answer these questions: search, list, stats and single-id lookups all filter valid_to IS NULL, so they only ever see the current state.

What the temporal columns actually mean

Read this before phrasing an answer — getting the axis wrong produces confident but false claims.

valid_from / valid_to track when the store recorded a version, not when the fact was true in the outside world. as_of=T answers "what did this memory store hold at T", not "what was true at T". If the user recorded a 2024 decision yesterday, it enters the timeline yesterday.
update does not edit in place. It closes the old row (valid_to = <update time>, superseded_by = <new id>) and inserts a new row with a new id and valid_from = <update time>. The id in the user's notes from last month no longer resolves through search.
delete also closes the row (valid_to set) but leaves superseded_by = NULL. That is the discriminator: a closed row with a forward pointer was replaced; without one it was retracted.
Rows created by add / capture carry valid_from = NULL; queries fall back to created_at via COALESCE. A null valid_from in a result means "original version", not a data defect.
commit_sha is present in the schema but is not populated by the current write paths. Do not present it as provenance.

Steps

Resolve the temporal anchor from the user's wording into a single UTC ISO timestamp: "last month" -> first day of that month, "before the migration" -> the timestamp of the migration memory, "at the time we chose X" -> the created_at of the decision memory. State the resolved timestamp in the answer so the user can correct it.
Take the point-in-time snapshot:
```
memory(action="as_of", as_of="2026-06-01T00:00:00+00:00", limit=50)
```
Returns rows satisfying valid_from <= as_of AND (valid_to IS NULL OR valid_to > as_of), newest first. as_of accepts no query filter, so raise limit (max 100) and filter by topic yourself over the returned content. Omitting as_of returns the current state instead.

Read the full file on GitHub · 138 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.

8d ago First seen · 138 lines · 77 tokens per session scan A 99dbeacf9b68

Subscribe to this mod's changes

temporal-query is a skill published in the GitHub repository n24q02m/mnemo-mcp (10 stars, last pushed today), licensed Apache-2.0. It adds 77 tokens to every session and 1,707 once invoked, about $0.0004 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.

Memory and context Python docker mcp mcp-server model-context-protocol open-source

scrape-batch

Extract many known URLs in one polite, rate-limited pass. Use when the user hands over a list of links, a set of search hits to read in full, or asks to "scrape these pages" / "pull the content from all of them". Drives extract(action="batch"), which fans out with per-domain rate limiting and returns partial results…

n24q02m/wet-mcp · 84 tokens

compare

Structured comparison of 2+ alternatives with consistent criteria and decision matrix.

n24q02m/wet-mcp · 15 tokens

research-topic

Multi-step research orchestration. Use when user asks "research X", "summarize current state of Y", "what's the latest on Z", or compares approaches. Calls extract(action="agent") which searches the web, extracts top results, then synthesises a citation-preserving Markdown answer with one configured LLM.

n24q02m/wet-mcp · 68 tokens

temporal-query