context

A command for adding descriptive notes to collections of documents in qmd, a local search system. These notes are shown with search results and can apply to a whole collection or selected folders.

In plain words
What is it for?
Use it to list, add, or remove collection notes and to attach shared or folder-specific guidance to search results.
Why use it?
It gives the search system extra information about what files or folders mean, helping an AI interpret results in context.

Command

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 commands/ramonclaudio/skills/context
Clone the repo
git clone --depth 1 https://github.com/ramonclaudio/skills
Per session 23 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 547 The whole file, excluding the scripts and references it only reads on demand.
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.00023 $0.00547
Opus 5 $0.00012 $0.00273
Sonnet 5 $0.00005 $0.00109
Haiku 4.5 $0.00002 $0.00055

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

Security

Grade A, and why

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

plugins/qmd/commands/context.md · 29 lines

What it actually says

Route based on the first token in $ARGUMENTS:

  • listqmd context list. Show all configured contexts grouped by collection.
  • add [path] "<text>"qmd context add $ARGUMENTS.
    • One-arg form (add "text") uses cwd and auto-detects the collection.
    • Two-arg form takes an explicit path. Path formats:
      • qmd://collection/path — virtual path inside a collection (recommended)
      • / — global context, applies to every collection
      • . or relative path — auto-resolved from cwd
      • Absolute filesystem path — collection detected by longest-prefix match
    • Collection names must match [a-zA-Z0-9_-]+.
  • rm <path> (alias remove) — qmd context rm $ARGUMENTS. Accepts both filesystem paths and qmd:// URIs.

Context is hierarchical: when a search hits a path, qmd concatenates ALL matching prefixes (global → root → specific subdir), joined with \n\n. Adding context at multiple levels is additive, not overriding.

What context actually does: the qmd MCP server returns the document's full hierarchical context block in every search result's context field. Claude (and other LLM callers) sees the context alongside the snippet so it knows what kind of document it's reading. Context is purely descriptive metadata. It does NOT influence chunk selection, reranking, or scoring — those are driven by the query terms and the optional intent parameter, not by the YAML context: field.

So context's job is to TELL the model "this snippet comes from a Convex schema example, not a tutorial blog post." A short, specific context (one sentence) is better than a long one because the full string gets prepended to every result's snippet.

The /qmd:add SKILL writes the initial root context once at clone/register time. Use this command to update the root context or add deeper paths later (e.g. qmd://next.js/docs/api → "Stable App Router API reference").

If $ARGUMENTS is empty or the subcommand is unrecognized, print: usage: /qmd:context <list|add|rm> [args].

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 · 29 lines · 23 tokens per session scan A 67d2080a24d9

Subscribe to this mod's changes

context is a command published in the GitHub repository ramonclaudio/skills (4 stars, last pushed 3mo ago), licensed MIT. It adds 23 tokens to every session and 547 once invoked, about $0.0001 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-31.