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 sbusso/claudeclaw --skill add-qmdgit clone --depth 1 https://github.com/sbusso/claudeclawWrote 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/sbusso/claudeclaw/add-qmd)<a href="https://agentmods.dev/skills/sbusso/claudeclaw/add-qmd"><img src="https://agentmods.dev/badge/skills/sbusso/claudeclaw/add-qmd/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/sbusso/claudeclaw/add-qmd"><img src="https://agentmods.dev/badge/skills/sbusso/claudeclaw/add-qmd.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00073 | $0.00613 |
| Opus 5.5 | $0.00029 | $0.00245 |
| Sonnet 5.5 | $0.00015 | $0.00123 |
| Haiku 4.5 | $0.00007 | $0.00061 |
Grade A, and why
add-qmd 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.
How it starts
The opening of the file, as written. The whole thing — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add QMD Memory Backend
QMD (https://github.com/tobi/qmd) is a local search engine for markdown files. It combines BM25 keyword search, vector semantic search, and LLM re-ranking — all running on-device via node-llama-cpp with GGUF models.
This skill upgrades ClaudeClaw's built-in grep-based memory_search MCP tool with QMD's hybrid search, giving agents much better recall across large memory collections.
Prerequisites
- ClaudeClaw with memory tools already working (memory_search, memory_save, memory_get)
- ~2GB disk space for GGUF embedding + reranking models (downloaded on first run)
- Node.js 20+
What This Skill Does
- Installs QMD as an MCP server dependency
- Configures QMD to index all group memory directories (
groups/*/memory/,groups/*/CLAUDE.md,groups/*/conversations/) - Replaces the grep-based
memory_searchinagent/runner/src/ipc-mcp-stdio.tswith QMD's API - Adds QMD indexing to the agent startup flow (incremental re-index on each run)
Implementation Notes
QMD MCP Server
QMD exposes its search as an MCP server. Add to the agent runner's mcpServers config:
qmd: {
command: 'npx',
args: ['qmd', 'mcp', '--collection', collectionPath],
env: {},
}
Indexing
QMD indexes markdown files into a local SQLite database. The collection should be configured per-group:
# Index a group's memory
qmd index --collection groups/{folder}/.qmd groups/{folder}/memory/ groups/{folder}/CLAUDE.md groups/{folder}/conversations/
Search Integration
Replace the grep-based memory_search tool body with a call to QMD's MCP:
// Before (grep-based):
const results = grepFiles(args.query, allFiles);
// After (QMD):
// Use the qmd MCP server's search tool
// Returns semantically ranked results with relevance scores
Fallback
If QMD is not installed or indexing fails, fall back to the built-in grep-based search. This ensures memory tools always work even without QMD.
Not Implemented Yet
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 · 68 lines · 73 tokens per session scan A 9f88144cbe8a
add-qmd is a skill published in the GitHub repository sbusso/claudeclaw (194 stars, last pushed 2mo ago), licensed MIT. It adds 73 tokens to every session and 613 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.
Other skills, from other repositories
persistent-notes
Save notes locally to /mnt/workspace/notes.json file. Use when user wants to "save a note" or "remember something".
llm-wiki
Build, ingest, query, and lint a persistent Markdown knowledge base using the Karpathy LLM Wiki pattern. Use for adding sources, maintaining interlinked wiki pages, answering from the knowledge base, filing durable research, or checking contradictions and index health. Do not use it to persist ordinary chat or…
awm-rsi-toolkit
Run AWM (Agent Workflow Memory, Wang et al. 2024) on an agent - induce reusable workflows from its successful trajectories, online over a training stream or offline from supplied experiences, then freeze the workflow memory and measure it on a published Benchmark.
memmachine-memory
Use when an agent or model needs durable project, user, or session context from MemMachine, needs to save information to MemMachine memory, has requests involving mem-cli, memmachine, or memmachineclient, has insufficient conversation context, or is tempted to search local files for prior context that should come from…
computer-history
Answer questions about what the user recently did on their computer — who contacted them, what they were working on, where they left off — by reading the local Computer History summaries and raw event streams.
docx
Create, read, edit, review, redline, comment on, merge, audit, render, and verify .docx Word documents, including layout-sensitive and OOXML-level work.