Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add gagharutyunyan1993/methodology-toolkit/plugin install methodology-toolkitWrote 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/gagharutyunyan1993/methodology-toolkit/methodology-driven-thinking)<a href="https://agentmods.dev/skills/gagharutyunyan1993/methodology-toolkit/methodology-driven-thinking"><img src="https://agentmods.dev/badge/skills/gagharutyunyan1993/methodology-toolkit/methodology-driven-thinking/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/gagharutyunyan1993/methodology-toolkit/methodology-driven-thinking"><img src="https://agentmods.dev/badge/skills/gagharutyunyan1993/methodology-toolkit/methodology-driven-thinking.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.00136 | $0.02530 |
| Opus 5 | $0.00068 | $0.01265 |
| Sonnet 5 | $0.00027 | $0.00506 |
| Haiku 4.5 | $0.00014 | $0.00253 |
Grade A, and why
methodology-driven-thinking 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 9d 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Methodology-Driven Thinking
This skill activates structured analytical methods when a task is non-trivial. The output of the skill is the reasoning produced by the methods, not the names of the methods.
Operating Protocol
Step 1 — Read the methodology index
Open ${CLAUDE_PLUGIN_ROOT}/skills/methodology-driven-thinking/methodology.md. This is the authoritative library with use_when, avoid_when, steps, and output for each method. Do not rely on memory — the index may have been updated.
Step 2 — Classify the problem (Cynefin as dispatcher)
Before selecting any other methodology, place the problem in a Cynefin domain:
- Clear / Simple — known cause-effect, best practice exists. → Exit the skill. Answer directly. Methodologies are tax, not insurance, on trivial tasks.
- Complicated — knowable through analysis/expertise. → Analytical methods fit (First Principles, ACH, 5 Whys, ToC, Porter, PMESII).
- Complex — cause-effect only visible in hindsight; requires probes. → Iteration methods fit (OODA, PDCA, Double Diamond, JTBD).
- Chaotic — no clear cause-effect. → Act first to stabilize, then re-classify.
State the classification in one line. If you can't classify, that itself is a signal — say so.
Step 2.5 — Evidence gate (load-bearing code claims)
This step runs after the Clear/Simple exit and before method selection — trivial tasks never reach it. If the task survived Step 2 and rests on a load-bearing claim about code — what a function returns, where a defect lives, what a command does, what the backend sends — gate the claim before any method consumes it:
- Name the claim explicitly: "This conclusion depends on X being true."
- Tag its current source tier — Primary (code you read, command output, git, test results), Secondary (
.d.ts, prose docs, comments — subject to drift), or Inferred (memory, assumption, analogy). - Promote every load-bearing claim to Primary before it enters a method: run the command, read the file, check git. A claim that stays Secondary/Inferred is a hypothesis, not an input.
What ships with it
2 files 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.
- 9d ago First seen · 108 lines · 136 tokens per session scan A ad9dde2535ef
methodology-driven-thinking is a skill published in the GitHub repository gagharutyunyan1993/methodology-toolkit (1 stars, last pushed 3mo ago), licensed MIT. It adds 136 tokens to every session and 2,530 once invoked, about $0.0007 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
devils-advocate
Utiliser avant toute décision importante pour faire jouer à l'IA le rôle d'un sceptique professionnel. Produit les trois meilleures raisons de ne pas faire ce qui est proposé, classées par force décroissante.
thinking-theory-of-constraints
When throughput or latency is pipeline-limited, identify the single binding constraint and exploit, subordinate, elevate, then recheck—ignore non-constraints.
docs-drift
Documentation-drift audit for this plugin monorepo. Audit either each scoped plugin's unreleased changelog claims or its latest shipped release from the previous reachable plugin-name--v tag, then verify that plugin READMEs, docs, CLAUDE.md or AGENTS.md files, and root documentation tell the truth for the matching…
cco-tools
Show what tools actually cost in tokens — learned per-tool averages from observed results, replacing the hardcoded MCP/Agent guesses.
github-pr-creation
Creates GitHub Pull Requests with automated validation and task tracking. Use when user wants to create PR, open pull request, submit for review, or check if ready for PR. Analyzes commits, validates task completion, generates Conventional Commits title and description, suggests labels. NOTE - for merging existing…
test-run
Run plugin test suites in this monorepo and report a concise pass/fail summary. Optional plugin slug arg; without arg, runs all plugins under plugins/.