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-assumptiongit 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-assumption)<a href="https://agentmods.dev/skills/tomzx/agents/review-assumption"><img src="https://agentmods.dev/badge/skills/tomzx/agents/review-assumption/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-assumption"><img src="https://agentmods.dev/badge/skills/tomzx/agents/review-assumption.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.00023 | $0.00793 |
| Opus 5 | $0.00012 | $0.00396 |
| Sonnet 5 | $0.00005 | $0.00159 |
| Haiku 4.5 | $0.00002 | $0.00079 |
Grade A, and why
review-assumption 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 6d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review Assumption
Audits an assumption record and reports findings across four categories: specificity, basis quality, risk assessment, and validation plan adequacy.
Prerequisites
- Apply the shared SDLC conventions in
skills/sdlc/references/shared.md. .sdlc/knowledge/assumptions/N-<slug>.md, or an assumption document provided in context or as a file path
Steps
- Read the assumption 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 terminal value:Validated(assumption confirmed),Invalidated(assumption disproved — flag affected work), orDeferred(cannot yet be verified).
Review Checklist
Specificity
- Is the assumption statement specific enough to be falsifiable?
- Does it name concrete scope (which users, which load, which environment)?
- Is the status field present and accurate?
Basis Quality
- Is there stated evidence or reasoning supporting the assumption?
- Is the confidence level consistent with the quality of the basis?
- If the basis is weak or absent, is that acknowledged rather than hidden?
Risk Assessment
- Is the impact level (High / Medium / Low) justified by the description?
- Does the risk description name specific components or flows that depend on the assumption?
- Are downstream assumptions or decisions that inherit this risk identified?
Validation Plan
- Is a concrete validation method described (not just "we'll check later")?
- Is there a named owner responsible for validation?
- Is there a deadline or milestone tied to validation?
- If the assumption cannot be validated before implementation, is that risk acknowledged?
Output Format
## Specificity
<Findings or "No issues found.">
## Basis Quality
<Findings or "No issues found.">
## Risk Assessment
<Findings or "No issues found.">
## Validation Plan
<Findings or "No issues found.">
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.
- 6d ago First seen · 99 lines · 23 tokens per session scan A 7e805722d710
review-assumption is a skill published in the GitHub repository tomzx/agents (6 stars, last pushed yesterday), licensed MIT. It adds 23 tokens to every session and 793 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…