clawql-vault-memory

A set of rules for using ClawQL, a memory service, to recall relevant past context and store important project knowledge when the service is available. It also covers where the service is configured and what information must not be stored.

In plain words
What is it for?
Recalling prior project context, recording structured insights after important outcomes, linking related notes, and avoiding storage of secrets or private keys.
Why use it?
It helps retain decisions, debugging findings, setup notes, and API details across sessions. It also provides boundaries for handling sensitive information.

Cursor rule for Cursor

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.

agentmods
npx agentmods add rules/danielsmithdevelopment/clawql/clawql-vault-memory
Clone the repo
git clone --depth 1 https://github.com/danielsmithdevelopment/ClawQL

Made for: Cursor.

Per session 451 This file is loaded in full into every session.
When invoked 451 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.00451 $0.00451
Opus 5 $0.00226 $0.00226
Sonnet 5 $0.00090 $0.00090
Haiku 4.5 $0.00045 $0.00045

Measured 2d ago against content hash f4d35700415a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

clawql-vault-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 2d 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.

.cursor/rules/clawql-vault-memory.mdc · 17 lines

What it actually says

ClawQL vault memory

When ClawQL MCP is available, use it deliberately:

  • call_mcp_tool: Use server user-clawql if ClawQL is configured in ~/.cursor/mcp.json, or workspace-clawql if it is only in .cursor/mcp.json in the repo. The mcpServers key remains clawql in JSON; Cursor prepends user- / workspace- for the agent API. Bare clawql is not accepted there.
  • memory_recall: At the start of non-trivial work, or when the user references past decisions, the vault, or missing context. Use a concrete query; keep limit reasonable; raise maxDepth when graph context matters.
  • memory_ingest: After important outcomes—decisions, debugging conclusions, env/setup notes, API contracts, user preferences, or links between topics. Prefer structured insights; put verbatim logs in toolOutputs; use wikilinks for the Obsidian graph; reuse title with append: true (default) to extend the same page.

Thorough ingests (rich structure, tagging in prose, wikilink strategy, session threading, anti-patterns): read and apply the project skill clawql-vault-memory.

Do not store secrets, credentials, or private keys. memory_ingest / memory_recall are registered by default; CLAWQL_ENABLE_MEMORY=0 hides them. A writable vault path is required for real I/O. If vault tools are missing or fail, say so briefly and continue without blocking the task.

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. 2d ago First seen · 17 lines · 451 tokens per session scan A f4d35700415a

Subscribe to this mod's changes

clawql-vault-memory is a cursor rule published in the GitHub repository danielsmithdevelopment/ClawQL (12 stars, last pushed 3d ago), licensed Apache-2.0. It adds 451 tokens to every session, about $0.0023 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-30.