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 skills add tomzx/agents --skill create-questiongit clone --depth 1 https://github.com/tomzx/agentsWrote 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/skills/tomzx/agents/create-question)<a href="https://agentmods.dev/skills/tomzx/agents/create-question"><img src="https://agentmods.dev/badge/skills/tomzx/agents/create-question/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/tomzx/agents/create-question"><img src="https://agentmods.dev/badge/skills/tomzx/agents/create-question.svg" alt="Reviewed on agentmods" width="80" 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.00027 | $0.00885 |
| Opus 5.5 | $0.00011 | $0.00354 |
| Sonnet 5.5 | $0.00005 | $0.00177 |
| Haiku 4.5 | $0.00003 | $0.00089 |
Grade A, and why
create-question 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 22d 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.
How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Question
Records an open question surfaced during the pipeline: what is being asked, the context where it arose, who can answer it, what work stalls without the answer, and when the answer is needed.
Questions differ from assumptions and decisions: an assumption is a belief held without verification; a decision is a deliberate choice between options; a question is missing information that a specific person, team, or source can supply.
Prerequisites
- Apply the shared SDLC conventions in
skills/sdlc/references/shared.md. - A question worth tracking: it blocks work or affects its direction, and the answer is not immediately available
- Enough context to say where it arose and who can answer it
Steps
- State the question clearly and specifically, so a named source could answer it as written.
- Describe the context: which feature, artifact, or phase surfaced it, and why the answer matters.
- Identify the answerer: who (person, team, vendor) or what (document, experiment) can answer, and how they will be reached.
- Assess what is blocked while the question stays open: which artifact, decision, or task waits on it.
- Set a needed-by date or milestone after which the block becomes costly.
- Save the document to
.sdlc/knowledge/questions/using the filename patternN-<slug>.mdwhereNis the next available number (counting existing files in that directory).
When the answer arrives, record it via /review-question.
When the answer cannot be obtained in time and work proceeds on a belief instead, promote the question to an assumption via /create-assumption.
When the answer requires choosing between options, record the choice via /create-decision and link it from the question.
Output Format
Use the template at skills/sdlc/templates/knowledge/question.md (copied to .sdlc/templates/knowledge/question.md by /initialize-sdlc-directory; use the project's customized copy if present).
Write the result to the artifact path named in the steps above.
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.
- 22d ago Changed · +1 lines 71dc7c28e797
- 23d ago Changed · -4 lines fe23b75fef52
- 24d ago Changed 47bad7b322a0
- 2mo ago First seen · 75 lines · 27 tokens per session scan A 48393c3aed72
create-question is a skill published in the GitHub repository tomzx/agents (13 stars, last pushed yesterday), licensed MIT. It adds 27 tokens to every session and 885 once invoked, about $0.0001 per session on Opus 5.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.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…