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 hajekim/agentic-design-patterns-extension --skill reasoninggit clone --depth 1 https://github.com/hajekim/agentic-design-patterns-extensionWrote 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/hajekim/agentic-design-patterns-extension/reasoning)<a href="https://agentmods.dev/skills/hajekim/agentic-design-patterns-extension/reasoning"><img src="https://agentmods.dev/badge/skills/hajekim/agentic-design-patterns-extension/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.00414 | $0.03881 |
| Opus 5 | $0.00207 | $0.01940 |
| Sonnet 5 | $0.00083 | $0.00776 |
| Haiku 4.5 | $0.00041 | $0.00388 |
Grade A, and why
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 7d 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.
This is a copy
100% identical to reasoning — 3 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 446 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reasoning Techniques Pattern
Overview
The Reasoning Techniques Pattern equips agents with structured approaches to thinking through problems before acting. Rather than jumping directly from input to output, reasoning-enhanced agents explicitly decompose problems, explore possibilities, verify their work, and reflect on their reasoning process — dramatically improving accuracy on complex tasks.
Core Principle: Slow down to speed up accuracy — structured thinking catches errors that fast pattern-matching misses.
When This Skill Applies
Activate this pattern when:
- Multi-step problems require logical deduction or causal reasoning
- Mathematical, coding, or analytical tasks require precise computation
- The agent must justify its conclusions (auditable decisions)
- Complex questions benefit from exploring multiple solution paths
- Self-consistency across multiple reasoning attempts is needed
- The agent must detect and correct its own errors before responding
Rule of thumb: If a human expert would "show their work" — the agent should too. Use reasoning techniques whenever accuracy matters more than speed.
Key Reasoning Techniques
1. Chain-of-Thought (CoT)
Break reasoning into explicit intermediate steps:
Problem → Step 1 → Step 2 → ... → Step N → Answer
2. ReAct (Reason + Act)
Interleave reasoning with tool use:
Thought → Action (tool call) → Observation → Thought → Action → ... → Answer
3. Tree of Thought (ToT)
Explore multiple reasoning branches and select the best:
Problem → Branch A → Branch B → Branch C
↓ (evaluate each)
Select Best Path → Answer
4. Self-Consistency
Generate multiple independent solutions, pick the majority answer:
Problem → Solution 1 → Answer A
→ Solution 2 → Answer A (consensus)
→ Solution 3 → Answer B
5. Self-Critique (Reflexion)
Agent critiques its own output and corrects it:
Problem → Initial Answer → Critique → Revised Answer → Critique → Final Answer
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.
- 7d ago First seen · 446 lines · 414 tokens per session scan A 5e9722f281a3
reasoning is a skill published in the GitHub repository hajekim/agentic-design-patterns-extension (1 stars, last pushed 5mo ago), licensed MIT. It adds 414 tokens to every session and 3,881 once invoked, about $0.0021 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to reasoning, differing in 3 lines, and is treated as a copy.
Other skills, from other repositories
prompt engineering
Use this skill when asked to create, refine, analyze, or optimize prompts for Large Language Models (LLMs). This skill ensures adherence to prompt engineering best practices and enforces a rigorous design workflow.
redteam
Expertise in offensive security research, vulnerability analysis, CMS-focused application testing, and red team operations.
redteam-source-audit
Focused source-code security review workflow for web applications, CMS extensions, APIs, and supporting services.
redteam-cms
Focused methodology for authorized CMS fingerprinting, component inventory, misconfiguration review, and vulnerability validation.
redteam-exploit-validation
Focused workflow for validating exploitability safely and turning candidate issues into reproducible, bounded proof.
redteam-recon
Focused reconnaissance workflow for authorized security assessments, bug bounty triage, lab targets, and CTF infrastructure.