meta

A command that checks whether a document is asking the right question. It can analyze pasted text or read a document from a file.

In plain words
What is it for?
Use it to review a question in a document or pasted text, then launch the question-review analysis.
Why use it?
It helps catch unclear or misguided questions before you spend time answering them. It also accepts an optional folder for saving the result.

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/ds1/probe/meta
Clone the repo
git clone --depth 1 https://github.com/ds1/probe
Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 414 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.00009 $0.00414
Opus 5 $0.00005 $0.00207
Sonnet 5 $0.00002 $0.00083
Haiku 4.5 $0.00001 $0.00041

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

Security

Grade A, and why

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

commands/meta.md · 35 lines

What it actually says

Probe: Question the Question

Run the question-the-question lens on one input. The lens prompt lives in the question-the-question agent; this command only parses arguments and launches it.

Arguments

$ARGUMENTS holds the input and, optionally, an output directory. Parse it in this order:

  1. If --out <dir> appears anywhere, that is the output directory. Remove it before the next step.
  2. If what remains starts with a quoted string, the quoted string is the input path. Otherwise, if the first whitespace-delimited token is an existing file, that token is the input path, and a second token (when present and no --out was given) is the output directory.
  3. If neither matched, the entire remaining text is the input, to be analyzed directly as pasted text.

Paths that contain spaces must be quoted.

Run

Use the Agent tool with subagent_type: "probe:question-the-question". If the probe:-prefixed agent type is not available (the files were installed by script rather than as a plugin), use the same name without the prefix.

Launch prompt:

  • Source: the input path, or the full pasted text.
  • Output: only if an output directory was given: <output-dir>/probe-question-the-question.md.
  • Grounding: if the source cites function names, constants, file paths, or schema columns, add: "Verify any specific code claims against the actual code at the cited paths; do not take the source's claims about its own codebase at face value."

Reply

If a file was written, give its path and relay the agent's summary. Otherwise relay the agent's full evaluation.

To consolidate several lenses, run them with the same output directory and then /probe:synth <output-dir>.

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 · 35 lines · 9 tokens per session scan A 54a17dae5fe0

Subscribe to this mod's changes

meta is a command published in the GitHub repository ds1/probe (2 stars, last pushed 5d ago), licensed MIT. It adds 9 tokens to every session and 414 once invoked, about $0.0000 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.