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 ConrayGambit/Strategy-Consultant-5-Consulting-Frameworks --skill mece-frameworkgit clone --depth 1 https://github.com/ConrayGambit/Strategy-Consultant-5-Consulting-FrameworksWrote 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/conraygambit/strategy-consultant-5-consulting-frameworks/mece-framework)<a href="https://agentmods.dev/skills/conraygambit/strategy-consultant-5-consulting-frameworks/mece-framework"><img src="https://agentmods.dev/badge/skills/conraygambit/strategy-consultant-5-consulting-frameworks/mece-framework/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/conraygambit/strategy-consultant-5-consulting-frameworks/mece-framework"><img src="https://agentmods.dev/badge/skills/conraygambit/strategy-consultant-5-consulting-frameworks/mece-framework.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.00058 | $0.00788 |
| Opus 5 | $0.00029 | $0.00394 |
| Sonnet 5 | $0.00012 | $0.00158 |
| Haiku 4.5 | $0.00006 | $0.00079 |
Grade A, and why
mece-framework 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MECE Framework
Concept
MECE — Mutually Exclusive, Collectively Exhaustive — is the foundation of structured problem solving:
- Mutually Exclusive: No factor belongs in two categories.
- Collectively Exhaustive: Every relevant factor is captured.
Non-MECE breakdowns look rigorous but aren't — overlapping categories double-count, and missing categories blind you to root causes.
Required output format
Nested Markdown bullets. Top-level bullets are categories in bold; nested bullets are the specific factors under each category.
- **Category 1**
- Sub-factor A
- Sub-factor B
- **Category 2**
- Sub-factor C
- Sub-factor D
Defaults & flex points
| Default | When to flex |
|---|---|
| 3–6 top-level categories | If the problem has only 2 real categories, use 2 — don't pad. If it has 7, use 7. |
| 2–5 sub-factors per category | Use as many as the problem actually contains. |
| Categories specific to the problem | Generic "People/Process/Technology" buckets are a smell — only use them if they genuinely fit. |
Rule that doesn't flex: the categories must be MECE. Test each one — could a factor reasonably belong to two? Then merge or split. Could relevant factors not fit anywhere? Then add a category.
Example — logistics
Problem: A regional courier company's on-time delivery rate fell from 94% to 81% in six months.
- **Network capacity**
- Vehicle fleet utilization (peak hour saturation)
- Driver headcount vs. demand
- Hub sortation throughput
- **Routing & dispatch**
- Algorithm changes after the Q2 system migration
- Address-data quality (geocoding errors)
- Manual route overrides by dispatchers
- **Demand pattern shift**
- New high-volume customer added in Q1
- Seasonal swing into peak retail months
- Same-day delivery share rising
- **Workforce**
- Driver turnover and onboarding ramp time
- Overtime caps from new labor agreement
- Sick days / absenteeism trend
- **External**
- Construction zones in two metro areas
- Two consecutive months of unusual weather
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 · 84 lines · 58 tokens per session scan A f27b0ccc1dfe
mece-framework is a skill published in the GitHub repository ConrayGambit/Strategy-Consultant-5-Consulting-Frameworks (23 stars, last pushed 3mo ago), licensed MIT. It adds 58 tokens to every session and 788 once invoked, about $0.0003 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
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.
Vizra ADK Memory System
Implement persistent memory, session context, and vector memory (RAG) for AI agents.
foundation-models
On-device LLM integration using Apple's Foundation Models framework. Use when implementing AI text generation, structured output, or tool calling.
analytics-interpretation
Interpret app metrics and make data-driven decisions. Covers DAU/MAU, retention, LTV, ARPU, App Store Connect analytics, AARRR funnel analysis, cohort analysis, and diagnostic decision trees. Use when user wants to understand their metrics, diagnose problems, or build a data-driven growth plan.
app-namer
Turn an app idea into validated, App-Store-ready name candidates. Use when the user says "name my app", "what should I call it", "app name ideas", "help me name this app", "is this name available", or needs to pick a brandable, ownable name before reserving it in App Store Connect.
in-app-events
Generates In-App Event metadata templates for App Store Connect — event names, descriptions, badge types, image specs, and deep link configuration. Use when creating events for App Store visibility, engagement campaigns, or seasonal promotions.