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 agentmods add skills/n24q02m/claude-plugins/temporal-querynpx 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.svg" alt="Measured on agentmods" 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 | $0.00077 | $0.01707 |
| Opus 5 | $0.00039 | $0.00853 |
| Sonnet 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 4d 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.
- 4d 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 (3 stars, last pushed yesterday), 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. It is 100% identical to temporal-query, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
flow-next-audit
Audit .flow/memory/ entries against current code and keep, update, consolidate, replace, delete, or harden each. Use when asked to audit memory or graduate a recurring lesson into a gate.
flow-next-audit
Audit .flow/memory/ entries against the current codebase and decide Keep / Update / Consolidate / Replace / Delete per entry. Triggers on /flow-next:audit, "audit memory", "review memory", "refresh learnings", "sweep stale memory", "consolidate overlapping memory entries". Optional mode:autofix token in arguments runs…
flow-next-memory-migrate
Migrate legacy flat .flow/memory files to the categorized YAML schema. One-time ceremony. Use when asked to migrate flow memory.
decision-ledger
Maintain an append-only decision ledger (DECISIONS.md). Use when the user confirms a decision, reverses or changes a past decision, asks what was decided and why, or at session start to load standing decisions.
knowledge-base
Keep verified findings in memory/knowledge/ so the same research is never done twice. Use before researching any topic, when a finding passes the verify gate, or when about to answer from something learned in an earlier session.
pin
Turn a correction or working preference the user just expressed into a permanent ballast rule. Use when the user corrects your behavior, says "don't do X" / "always do Y" / "I told you before", or asks you to remember how they want things done.