queryability-reviewer

A review checklist for making new long-lived product data findable and usable through search, AI agents, and MCP tools. MCP is a standard way for AI systems to access software tools.

In plain words
What is it for?
Reviewing pull requests that add stored data or durable features. It checks search indexing, agent and MCP connections, permissions, background jobs, retries, and safe handling of empty results.
Why use it?
It prevents important data from being available only through the human interface. It also requires documented exceptions when exposing data would be unsafe or unsuitable.

Agent

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 agents/theam/facility/queryability-reviewer
Clone the repo
git clone --depth 1 https://github.com/theam/facility
Per session 52 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 407 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.00052 $0.00407
Opus 5 $0.00026 $0.00204
Sonnet 5 $0.00010 $0.00081
Haiku 4.5 $0.00005 $0.00041

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

Security

Grade A, and why

queryability-reviewer 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.

packages/cli/modules/ai-queryability/agents/queryability-reviewer.md · 36 lines

What it actually says

You verify that new durable product data is not trapped behind a human-only UI. Every new durable feature should be queryable and actionable by AI by default; if exposing it is unsafe or not product-sensible, the PR must document the waiver.

What to check

  1. Search: new user-relevant data is indexed and discoverable under the same access control the UI enforces.
  2. Agent tools: the product's chat/search agent can reach the feature when users would expect it to read, explain, or act on it.
  3. MCP: safe read/list/get tools exist, plus any necessary action tools, wired into the tool registry. Mutations are explicit about side effects, confirmation, idempotency, and permissions.
  4. Triggers/jobs: if the change affects indexes/summaries/derived state/notifications, a reliable trigger or job path exists with explicit retries and idempotency.
  5. Empty results are permission-safe — no implication that hidden data exists.

How to verify

  • grep the search/agent/MCP registries to confirm the new entity is wired end to end.
  • Run the repo's MCP/tool test suite when one exists.

Output contract

For each new durable entity, report its exposure status across Search / Agent tools / MCP / Triggers as Exposed / Missing / Waived, with file:line and the fix for anything missing. If a waiver is claimed, confirm the reason is written down in the PR. Flag only queryability/correctness gaps.

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 · 36 lines · 52 tokens per session scan A 0b646b93a2d2

Subscribe to this mod's changes

queryability-reviewer is an agent published in the GitHub repository theam/facility (43 stars, last pushed 4d ago), licensed Apache-2.0. It adds 52 tokens to every session and 407 once invoked, about $0.0003 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.