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.
npx skills add n24q02m/claude-plugins --skill temporal-querygit clone --depth 1 https://github.com/n24q02m/claude-pluginsWrote 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.
[](https://agentmods.dev/skills/n24q02m/claude-plugins/temporal-query)<a href="https://agentmods.dev/skills/n24q02m/claude-plugins/temporal-query"><img src="https://agentmods.dev/badge/skills/n24q02m/claude-plugins/temporal-query/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.
<a href="https://agentmods.dev/skills/n24q02m/claude-plugins/temporal-query"><img src="https://agentmods.dev/badge/skills/n24q02m/claude-plugins/temporal-query.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.5 | $0.00031 | $0.00683 |
| Sonnet 5.5 | $0.00015 | $0.00341 |
| Haiku 4.5 | $0.00008 | $0.00171 |
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 1mo 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.
This is a copy
100% identical to temporal-query — 0 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.
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_totrack when the store recorded a version, not when the fact was true in the outside world.as_of=Tanswers "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.updatedoes 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 andvalid_from = <update time>. The id in the user's notes from last month no longer resolves throughsearch.deletealso closes the row (valid_toset) but leavessuperseded_by = NULL. That is the discriminator: a closed row with a forward pointer was replaced; without one it was retracted.- Rows created by
add/capturecarryvalid_from = NULL; queries fall back tocreated_atviaCOALESCE. Anullvalid_fromin a result means "original version", not a data defect. commit_shais 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_atof 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_ofaccepts no query filter, so raiselimit(max 100) and filter by topic yourself over the returned content. Omittingas_ofreturns the current state instead.
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.
- 1mo ago First seen · 138 lines · 77 tokens per session scan A 99dbeacf9b68
temporal-query is a skill published in the GitHub repository n24q02m/claude-plugins (4 stars, last pushed today), licensed Apache-2.0. It adds 77 tokens to every session and 1,707 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to temporal-query, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
catchup
Restore context after /clear by summarizing recent work and project state.
moai-mx
Scan codebase and add @MX code-level annotations for AI context.
start
Load session context — git state, backlog, last handoff.
weekly-digests
Generate a serial week-by-week narrative digest of a project's full claude-mem timeline. Splits the timeline into per-ISO-week files, then runs one consecutive subagent per week — each receiving the prior week's carry-forward block — to produce one chapter per ISO week of data. Use when asked for "weekly digests"…
cloud-sync
Set up or check claude-mem cloud sync with cmem.ai Pro. Use when the user says "set up cloud sync", "sync my memories", "cmem pro", "cloud backup", "sync status", or wants their memory database backed up or synced to their cmem.ai account.
long-context
Extend context windows of transformer models using RoPE, YaRN, ALiBi, and position interpolation techniques. Use when processing long documents (32k-128k+ tokens), extending pre-trained models beyond original context limits, or implementing efficient positional encodings. Covers rotary embeddings, attention biases…