query-memory

query-memory is a skill for Codex from frenzymath/Danus. It costs 68 tokens per session (761 once invoked), scanned A, original, Apache-2.0.

A memory lookup step that searches previous reasoning, shared findings, verified mathematical facts, and known dead ends before new work begins.

In plain words
What is it for?
Finding earlier conclusions, counterexamples, verification results, reusable proofs, and project definitions relevant to a new question.
Why use it?
It reduces repeated effort and helps avoid approaches that have already failed or claims that have not been verified.

Skill for Codex

Written for Codex: agents/openai.yaml present.

Good fit Finding earlier conclusions, counterexamples, verification results, reusable proofs, and project definitions relevant to a new question.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/frenzymath/danus/query-memory
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 frenzymath/Danus --skill query-memory
Clone the repo
git clone --depth 1 https://github.com/frenzymath/Danus

Made for: Codex.

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/frenzymath/danus/query-memory/github.svg)](https://agentmods.dev/skills/frenzymath/danus/query-memory)
Your own site
<a href="https://agentmods.dev/skills/frenzymath/danus/query-memory"><img src="https://agentmods.dev/badge/skills/frenzymath/danus/query-memory/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 query-memory

Your own site · 80×15
<a href="https://agentmods.dev/skills/frenzymath/danus/query-memory"><img src="https://agentmods.dev/badge/skills/frenzymath/danus/query-memory.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 68 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 761 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00068 $0.00761
Opus 5.5 $0.00027 $0.00304
Sonnet 5.5 $0.00014 $0.00152
Haiku 4.5 $0.00007 $0.00076

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

Security

Grade A, and why

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

agents/skills/worker/query-memory/SKILL.md · 60 lines

How it starts

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

Query Memory

Before spending effort, check what already exists. There are three places to look, in the three-memory model:

  1. Your own local memory (private): read/grep local_memory/notes.jsonl and events.jsonl for your prior reasoning and what you already tried.
  2. Global memory (shared findings): gm_search(query, kinds=...) over the swarm's findings. Especially useful kinds:
    • dead_end / obstacle — paths that already died (skip them);
    • verification — outcomes of others' fact_submit (learn from rejections);
    • conclusion / example / counterexample / plan — others' results to build on. You can also read the global_memory/<kind>.jsonl files directly.
  3. Fact graph (verified truth): fact_search(query) (BM25 over the verified facts) to find results you can cite or that show your subgoal is already proved — it returns {fact_id, statement}; read the full proof from fact_graph/facts/<fact_id>.md on a relevant hit, and fact_graph/glossary.json to reuse the project's symbol definitions. A proof may build only on facts (cite a fact_id).

Procedure

  1. Obey the current prompt's restrictions first. If it forbids a direction, file, or search, that overrides default recall. If it recommends specific results or directions, raise their priority.
  2. Start with the cheapest relevant source: your own local memory for your context; gm_search for the swarm's findings; the fact graph for verified building blocks.
  3. Prefer a narrow, targeted query (specific kinds, a sharp query string) over reading everything.
  4. Workspace boundary: stay inside your own working directory and the shared project stores. Do not scan parent directories, other workers' private local_memory/, or other projects.

Retrieval priority

  • A relevant verified fact (fact graph) is the strongest hit — you can build on it directly by citing its fact_id.
  • A sibling's dead_end/obstacle saves you from re-walking a dead path.
  • A sibling's verification rejection tells you why a similar claim failed.
  • A conclusion/example/counterexample is awareness — useful, but never a brick (only facts are). Re-verify anything you intend to build on.

Read the full file on GitHub · 60 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 1mo ago First seen · 60 lines · 68 tokens per session scan A 17a6355fdf1f

Subscribe to this mod's changes

query-memory is a skill published in the GitHub repository frenzymath/Danus (483 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 68 tokens to every session and 761 once invoked, about $0.0003 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

Other skills, from other repositories

knowledge_store_skill

Skill for working with local .knowledge.yaml files via KnowledgeStore. Use this when you need to recall, search, or manage directory-local memories and knowledge links stored in plain YAML alongside the user's project files. KnowledgeStore is directory-scoped. Each directory that contains a .knowledge.yaml file…

NPC-Worldwide/npcpy · 346 tokens

cocoscout

Relevance-ranked context loading — Tier 2 async subagent (Haiku, <5s) that fires after Tier 1 deterministic checks in UserPromptSubmit. Injects ranked context from CocoGrove, CocoContext, Environment Inspector, Prompt Studio, and CocoDream.

Snowflake-Labs/cocoplus · 59 tokens

pod-checkpoint

Write a structured recovery snapshot to lifecycle/checkpoint.md before context reset — captures phase, stage, decisions, and pending items so $pod resume can restore precise context.

Snowflake-Labs/cocoplus · 36 tokens

cocohealth

Context utilization monitor — background monitor that samples context window utilization via PostToolUse hook, surfaces advisory at 60% and critical warning with recovery decision matrix at 70%.

Snowflake-Labs/cocoplus · 38 tokens

pod-resume

Reconstruct context for a returning developer. Reads .cocoplus/ state and generates a narrative summary of project status, last achievements, pending tasks, recent decisions, available patterns, CocoCupper insights, and recommended next action.

Snowflake-Labs/cocoplus · 50 tokens

pull-search

CocoPull session archive search — full-text search across past sessions. Handles $pull search " " with --since and --feature filters, and $pull index rebuild.

Snowflake-Labs/cocoplus · 38 tokens