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 yegor256/critic --skill analyze-argumentation-flowgit clone --depth 1 https://github.com/yegor256/criticWrote 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/yegor256/critic/analyze-argumentation-flow)<a href="https://agentmods.dev/skills/yegor256/critic/analyze-argumentation-flow"><img src="https://agentmods.dev/badge/skills/yegor256/critic/analyze-argumentation-flow/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/yegor256/critic/analyze-argumentation-flow"><img src="https://agentmods.dev/badge/skills/yegor256/critic/analyze-argumentation-flow.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.00622 |
| Opus 5 | $0.00015 | $0.00311 |
| Sonnet 5 | $0.00006 | $0.00124 |
| Haiku 4.5 | $0.00003 | $0.00062 |
Grade A, and why
analyze-argumentation-flow 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 10d 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reading
Read whole text once before flagging anything. Reconstruct central thesis in one sentence. Do this even when author never states it. Report missing thesis as finding when you cannot reconstruct it.
Scope
List supporting claims in order and note evidence for each.
Judge argument author makes, not one you wish they made.
Distinguish flaws of reasoning from flaws of taste.
Distinguish the conclusion is wrong from the argument is weak.
Report only second kind.
Claims
Flag every factual claim without support. Surface unstated premises argument leans on. Check every key term for equivocation.
Inference
Test inference at every therefore, so, thus, or hence.
Test it at every which means or as a result too.
Hunt for circular reasoning.
Check each premise's independent believability.
Fallacies
Name specific fallacies and quote triggering line.
Use names from references/fallacies.md.
Treat one anecdote as one anecdote.
Watch for cherry-picked evidence and survivorship bias.
Mark every analogy and ask where it breaks.
Rhetoric
Flag rhetorical questions that stand in for arguments.
Treat obviously, clearly, and everyone knows as red flags.
Treat it goes without saying and as we all agree same way.
Watch for loaded language replacing evidence.
Counterargument
Check author addresses strongest counterargument. Use one fair opponent would raise. Notice when burden of proof shifts onto reader.
Structure
Hunt for contradictions across paragraphs. Compare introduction's promise against conclusion's delivery. Flag restated claims that add no evidence, distinction, or consequence. Notice scope creep, where narrow claim inflates into sweeping one. Check order of reasoning. Distinguish description from prescription.
Fairness
Forgive slips that leave conclusion intact and challenge load-bearing ones. Raise only objections honest reader would make.
Report
Report findings as numbered list. Give quoted snippet and fallacy name in each item. Add one-sentence explanation and one-line remedy. End with one-paragraph verdict. Name which load-bearing claims survive and whether thesis stands.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 106 lines · 29 tokens per session scan A 1c194c7de21f
analyze-argumentation-flow is a skill published in the GitHub repository yegor256/critic (4 stars, last pushed 4d ago), licensed MIT. It adds 29 tokens to every session and 622 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-08-31.
Other skills, from other repositories
chief-strategy-officer
Owns where the business plays and how it wins over a multi-year horizon — portfolio choices, corporate development, strategic partnerships, and planning under uncertainty. Use this for a decision about which markets or businesses to be in, whether to build, buy, or partner, how to allocate capital across business…
seo-strategy
Audits and improves organic search performance — technical health, site architecture, internal linking, structured data, and the content decisions that determine what can rank. Use this to run an SEO audit, diagnose why pages are not ranking or were deindexed, plan a site's URL and navigation structure, add structured…
customer-success-management
Runs the ongoing relationship with accounts after the sale — segmenting coverage against account value, building a health score that predicts rather than describes, running reviews customers find worth attending, forecasting renewals honestly, and finding expansion that follows usage instead of quota. Use this to…
chief-financial-officer
Owns the financial position: planning, budgeting, forecasting, unit economics, cash, and the numbers the business is run and reported on. Use this to build or challenge a budget, model a decision's financial consequence, assess unit economics or runway, evaluate an investment or spend request, set financial controls…
service-desk
Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…
telephony-and-conferencing
Runs voice and meeting infrastructure — phone systems and numbers, emergency calling obligations, conference rooms and their AV, call recording and its retention consequences, and the porting that makes provider changes go badly. Use this to replace a phone system, fix rooms nobody can start a meeting in, meet…