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 agentmods add commands/ds1/boilerplate.md/probe-qqgit clone --depth 1 https://github.com/ds1/boilerplate.mdWrote 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/commands/ds1/boilerplate.md/probe-qq)<a href="https://agentmods.dev/commands/ds1/boilerplate.md/probe-qq"><img src="https://agentmods.dev/badge/commands/ds1/boilerplate.md/probe-qq.svg" alt="Measured on agentmods" height="20"></a>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.00000 | $0.00268 |
| Opus 5 | $0.00000 | $0.00134 |
| Sonnet 5 | $0.00000 | $0.00054 |
| Haiku 4.5 | $0.00000 | $0.00027 |
Grade A, and why
probe-qq 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 5d 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.
What it actually says
Probe: Question the Question
Analyze a document by questioning the question itself.
Usage
/probe-qq <path-to-document>
Prompt
You are a Socratic analyst specializing in questioning the question itself.
Read the document at: $ARGUMENTS
Create a detailed Socratic evaluation that:
- Examines the framing - Is this the right question to ask? What does it assume?
- Challenges scope - Why these options and not others? Is the scope too narrow or too broad?
- Questions timing - Is now the right time? What information would help?
- Explores meta-questions - What's the real problem being solved? Is this approach necessary?
- Identifies questions not asked - What important questions were overlooked?
- Proposes alternative framing - What questions might lead to better clarity?
Structure your evaluation with:
- Analysis of the question's embedded assumptions
- Alternative questions that might be more useful
- Meta-level strategic considerations
- Reframed decision framework
Output the evaluation as markdown.
By @ds1 — from socratic-probes
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.
- 5d ago First seen · 36 lines · 0 tokens per session scan A a215cd2a75aa
probe-qq is a command published in the GitHub repository ds1/boilerplate.md (5 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 268 tokens. 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.
Other commands, from other repositories
create-pr
Create a pull request following the official template.
review-code
Read ALL memory bank code rules + best practices, check the files that changed, and APPLY fixes so they adhere. The active counterpart to /scan (which is read-only). Use after an AI session, before commit, to make changed files compliant.
learn
Command "learn" from chohra-med/expo_boilerplate, covering command: learn — the learning loop (feedback → rules), when to run it, invocation, the loop (6 steps) and 1 — capture.
migrate
Command "migrate" from chohra-med/expo_boilerplate, covering invocation, steps and rule.
audit
Command "audit" from chohra-med/expo_boilerplate, covering invocation, checks and output.
build
Command "build" from chohra-med/expo_boilerplate, covering command: build — run the sdd pipeline over tasks.md, invocation, per-task cycle, gates (constitution) and output.