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-articlegit 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-article)<a href="https://agentmods.dev/skills/tomzx/agents/review-article"><img src="https://agentmods.dev/badge/skills/tomzx/agents/review-article/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-article"><img src="https://agentmods.dev/badge/skills/tomzx/agents/review-article.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.01022 |
| Opus 5 | $0.00014 | $0.00511 |
| Sonnet 5 | $0.00005 | $0.00204 |
| Haiku 4.5 | $0.00003 | $0.00102 |
Grade A, and why
review-article 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review Article
Audits an article and reports findings across seven categories: accuracy, clarity, structure, sourcing, audience fit, cross-article consistency, and style. Each finding is prioritized with 🔴 MUST fix, 🟡 SHOULD fix, or 🟢 MAY fix.
Prerequisites
- Article provided in context or as a file path to read
- Target audience (if known, improves audience-fit check)
- Relevant sources (optional, improves accuracy check)
- Other related articles in the same series (optional, enables cross-article consistency checks)
Steps
- Read the article thoroughly.
- Cross-reference claims against provided sources if available.
- Compare claims, figures, and terminology against other related articles in context if available.
- Identify issues in each category below.
- Prioritize each finding: 🔴 MUST, 🟡 SHOULD, 🟢 MAY.
- Report findings using the output format. Omit categories with no findings.
Review Checklist
Accuracy
- Are factual claims correct and verifiable?
- Are statistics, numbers, and dates accurate?
- Are technical concepts described correctly?
- Are attributed claims accurately representing their sources?
Clarity
- Does the article open with the most important point, not background?
- Is every sentence necessary, with no filler or padding?
- Are abstract points anchored with concrete examples, numbers, or comparisons?
- Is jargon avoided or defined on first use?
Structure
- Does the article follow a logical progression from hook to takeaway?
- Are sections focused on a single idea each?
- Is there a clear through-line connecting all sections?
- Does the ending provide something actionable or memorable (not a weak summary)?
Sourcing
- Are claims attributed to sources with hyperlinks, not just textual citations?
- Are all hyperlinks verified (no 404s or broken references)?
- Are opinions clearly distinguished from sourced facts?
- Are sources credible and relevant?
Audience Fit
- Is the tone appropriate for the stated or implied audience?
- Is the depth calibrated: neither too shallow nor too detailed?
- Does the article assume appropriate prior knowledge?
- Would the target audience find this valuable?
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 · 142 lines · 27 tokens per session scan A 251f7fb3449b
review-article is a skill published in the GitHub repository tomzx/agents (6 stars, last pushed yesterday), licensed MIT. It adds 27 tokens to every session and 1,022 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…