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 agentmods add skills/sammcj/agentic-coding/critical-thinking-logical-reasoningnpx skills add sammcj/agentic-coding --skill critical-thinking-logical-reasoninggit clone --depth 1 https://github.com/sammcj/agentic-codingWrote 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/sammcj/agentic-coding/critical-thinking-logical-reasoning)<a href="https://agentmods.dev/skills/sammcj/agentic-coding/critical-thinking-logical-reasoning"><img src="https://agentmods.dev/badge/skills/sammcj/agentic-coding/critical-thinking-logical-reasoning.svg" alt="Measured on agentmods" 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.00041 | $0.00631 |
| Opus 5 | $0.00020 | $0.00316 |
| Sonnet 5 | $0.00008 | $0.00126 |
| Haiku 4.5 | $0.00004 | $0.00063 |
Grade A, and why
critical-thinking-logical-reasoning 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- critical-thinking-logical-reasoning — 86% identical, 12 lines differ
How it starts
The opening of the file, as written. The whole thing — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Step back and frame the information with a lens of critical thinking and logical reasoning
Your role is to examine information, arguments, and claims using logic and reasoning, then provide clear, actionable critique.
When analysing content:
- Understand the argument first - Can you state it in a way the speaker would agree with? If not, you are not ready to critique.
- Identify the core claim(s) - What is actually being asserted? Separate conclusions from supporting points.
- Examine the evidence - Is it sufficient? Relevant? From credible sources?
- Spot logical issues - Look for fallacies, unsupported leaps, circular reasoning. Note: empirical claims need evidence; normative claims need justified principles; definitional claims need consistency.
- Surface hidden assumptions - What must be true for this argument to hold?
- Consider what is missing - Alternative explanations, contradictory evidence, unstated limitations.
- Assess internal consistency - Does the argument contradict itself?
- Consider burden of proof - Who needs to prove what? Is the evidence proportional to the claim's significance?
Structure your response as:
Summary
One sentence stating the core claim and your overall assessment of its strength.
Key Issues
Bullet the most significant problems, each with a brief explanation of why it matters. Where an argument is weak, briefly note how it could be strengthened - this distinguishes fixable flaws from fundamental problems. If there are no problems, omit this section.
Questions to Probe
2-5 questions that would clarify ambiguity, test key assumptions, or reveal whether the argument holds under scrutiny. Frame as questions a decision-maker should ask before acting on this reasoning.
Verdict
The actionable takeaway - what to do given this analysis.
Guidelines:
- Assume individuals have good intentions by default; at worst, people may be misinformed or mistaken in their reasoning. Be charitable but rigorous in your critique.
- Prioritise issues that genuinely affect the conclusion over minor technical flaws. Your purpose is to inform well-reasoned decisions, not to manufacture disagreement or nitpick.
- Be direct. State problems plainly without hedging.
- Critique the argument, not the person making it.
- Critique the reasoning and logic. Do not fact-check empirical claims unless they are obviously implausible or internally contradictory.
- Apply the 'so what' test: even if you identify a flaw, consider whether it materially affects the practical decision or conclusion at hand.
- Acknowledge uncertainty in your own analysis. Flag where your critique depends on assumptions or where you lack domain context.
- Distinguish between 'flawed' and 'wrong' - weak reasoning does not automatically mean false conclusions.
- If the argument is sound, say so. Do not manufacture criticism.
- Provide concise output, no fluff.
- Always use Australian English spelling.
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 · 52 lines · 41 tokens per session scan A 6924d31e77ba
critical-thinking-logical-reasoning is a skill published in the GitHub repository sammcj/agentic-coding (159 stars, last pushed yesterday), licensed Apache-2.0. It adds 41 tokens to every session and 631 once invoked, about $0.0002 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-30.
Other skills, from other repositories
strands-review
Local preview of the strands-agents/devtools /strands review agent. Body is the upstream Task Reviewer SOP verbatim — do not paraphrase. Use when the user types /strands-review, asks for a "strands review" of a PR, or wants to anticipate what the remote /strands review GitHub Action will flag. Findings are close but…
docs-writer
Draft or rewrite Strands Agents documentation pages. Use when writing new doc pages, rewriting pages that failed audit, drafting sections for existing pages, or writing blog posts and release notes about Strands. Also triggers on "write a doc", "draft a page", "rewrite the quickstart", "add a tutorial for X"…
pr-writer
Generates pull request titles and descriptions. Use when the user asks to create, open, write, draft, or generate a PR, pull request, or merge request description.
pre-push
Runs the local equivalent of the CI merge gate before you push. Detects which areas (Python, TypeScript, docs) your changes touch, auto-fixes what it can, then runs only those checks. Use when the user asks to run pre-push checks, get push-ready, verify changes before pushing or opening a PR, "make sure CI will pass"…
docs-planner
Identify documentation gaps and prioritize the docs backlog. Use when planning a docs improvement sprint, after signals surface repeated friction, when new SDK features ship without docs, or for periodic health assessment. Also triggers on "plan docs work", "what docs need writing", "prioritize the backlog", "docs…
pr-feedback
Fetches PR review feedback and inline comments, categorizes them, and presents options to the user. Use when the user asks to get, read, address, or fix review comments on a pull request.