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 review-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/review-question)<a href="https://agentmods.dev/skills/tomzx/agents/review-question"><img src="https://agentmods.dev/badge/skills/tomzx/agents/review-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/review-question"><img src="https://agentmods.dev/badge/skills/tomzx/agents/review-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.00029 | $0.00940 |
| Opus 5.5 | $0.00012 | $0.00376 |
| Sonnet 5.5 | $0.00006 | $0.00188 |
| Haiku 4.5 | $0.00003 | $0.00094 |
Grade A, and why
review-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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review Question
Audits a question record and reports findings across five categories: specificity, context, answerability, impact and urgency, and resolution quality. When an answer is available, records it in the Answer section and closes the question.
Prerequisites
- Apply the shared SDLC conventions in
skills/sdlc/references/shared.md. .sdlc/knowledge/questions/N-<slug>.md, or a question document provided in context or as a file path
Steps
- Read the question document.
- Evaluate it against the checklist below.
- Report findings by category. Omit categories with no findings.
- After the review, update
statusin frontmatter to the appropriate value:Resolved(answer recorded in the Answer section),Deferred(cannot be answered yet; risk acknowledged and a revisit date set), orDismissed(no longer relevant; reason recorded in the Answer section). LeaveOpenwhen no resolution applies yet.
Review Checklist
Specificity
- Is the question stated so a named source could answer it directly?
- Does it name concrete scope (which system, which plan, which environment)?
- Is the status field present and accurate (Open | Resolved | Deferred | Dismissed)?
Context
- Does the context say which feature, artifact, or phase surfaced the question?
- Is it clear why the answer matters to that work?
Answerability
- Is an answerer named (person, team, vendor) or an authoritative source (document, experiment)?
- Is the channel or method for obtaining the answer described?
- If the question is answerable from the codebase or docs alone, is a tracked record even needed?
Impact and Urgency
- Is the blocking level (High / Medium / Low) justified by the description?
- Does the record name the artifact, decision, or task that waits on the answer?
- Is a needed-by date or milestone present, and is an overdue date flagged?
Resolution Quality
- If status is Resolved: does the Answer section answer the question as asked?
- Is the answer's source and date recorded?
- If the answer requires choosing between options, is the decision recorded via
/create-decisionand linked? - If work proceeds on the unverified answer, is it promoted via
/create-assumptionand linked?
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 · -2 lines a27436c86b0f
- 23d ago Changed · -4 lines 673fe8cf1655
- 24d ago Changed 7c9ace6cb691
- 1mo ago First seen · 108 lines · 29 tokens per session scan A 14dfc226c149
review-question is a skill published in the GitHub repository tomzx/agents (13 stars, last pushed yesterday), licensed MIT. It adds 29 tokens to every session and 940 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-09-03.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.