cq:status

A command that shows statistics for the cq knowledge store, including where knowledge is stored, its subject areas, recent local additions, and confidence levels.

In plain words
What is it for?
Use it to inspect local, private, and public knowledge counts, review recent additions, see confidence ranges, and list the store's domains.
Why use it?
It gives a quick view of the size, distribution, and recent activity of the stored technical knowledge.

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/mozilla-ai/cq/status
Clone the repo
git clone --depth 1 https://github.com/mozilla-ai/cq
Per session 27 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 612 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.00027 $0.00612
Opus 5 $0.00014 $0.00306
Sonnet 5 $0.00005 $0.00122
Haiku 4.5 $0.00003 $0.00061

Measured yesterday against content hash 8b31b3af5beb, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

cq:status 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 yesterday.

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/cq/commands/status.md · 61 lines

How it starts

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

/cq:status

Display a summary of the cq knowledge store.

Instructions

  1. Call the status MCP tool (no arguments needed).
  2. Format the response as a readable summary using the sections below.

Output Format

Present the results using this structure:

## cq Knowledge Store

### Tier Counts
local: {count} | private: {count} | public: {count}

*local* = on this machine only; *private* = shared with everyone who can reach the same `CQ_ADDR`; *public* = the open commons, shared across every node that participates in it (available when your configured remote serves it).

### Recent Local Additions
- {id}: "{summary}" ({relative time})
- ...

### Confidence Distribution
*(covers local plus your private/org units; excludes the public commons)*

■ 0.7-1.0: {count} units
■ 0.5-0.7: {count} units
■ 0.3-0.5: {count} units
■ 0.0-0.3: {count} units

### Domains
{distinct count} total
{domain} ({count}), {domain} ({count}) ... +{remaining} more

The tier_counts field contains the tier breakdown. Display all tiers present in the response. Omit tiers with a count of 0.

The recent field reflects the local store only. When a remote is configured and reachable, units proposed via Client.Propose go directly to the remote and do not appear here. If recent is empty, render the section as (no recent local additions) so users understand the scope.

The domain_counts field maps each domain to its unit count. Domains are the least important section, so render them last and keep them compact: a {distinct count} total line, then the most-tagged few on the next line as {domain} ({count}) (highest count first, ties alphabetical), capped at 8. If more than 8 exist, append the truncation marker after a single space, e.g. {domain} ({count}) ... +{remaining} more; do not leave a trailing comma before it.

If the warnings field is non-empty, surface each entry prominently above the summary so the counts are not mistaken for the full picture. A warning means stats aggregation degraded; for example, an unreachable or misconfigured remote, in which case the counts reflect the local store only:

Read the full file on GitHub · 61 lines

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. yesterday First seen · 61 lines · 27 tokens per session scan A 8b31b3af5beb

Subscribe to this mod's changes

cq:status is a command published in the GitHub repository mozilla-ai/cq (1,258 stars, last pushed 17d ago), licensed Apache-2.0. It adds 27 tokens to every session and 612 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-30.