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 fatihguner/foreman --skill defining-and-exploring-problemsgit clone --depth 1 https://github.com/fatihguner/foremanWrote 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/fatihguner/foreman/defining-and-exploring-problems)<a href="https://agentmods.dev/skills/fatihguner/foreman/defining-and-exploring-problems"><img src="https://agentmods.dev/badge/skills/fatihguner/foreman/defining-and-exploring-problems/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/fatihguner/foreman/defining-and-exploring-problems"><img src="https://agentmods.dev/badge/skills/fatihguner/foreman/defining-and-exploring-problems.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00124 | $0.04404 |
| Opus 5.5 | $0.00050 | $0.01762 |
| Sonnet 5.5 | $0.00025 | $0.00881 |
| Haiku 4.5 | $0.00012 | $0.00440 |
Grade A, and why
defining-and-exploring-problems 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 1mo 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 — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Read runtime and advisory rules before applying this skill. Other Foreman layers and the catalog are in ../../content/, relative to this SKILL.md.
Defining and Exploring Problems
WRONG PROBLEM. Most failed decisions do not come from wrong answers -- they come from wrong questions. A room of intelligent people converges on a plausible-sounding problem statement within minutes, pivots immediately to solutions, and spends weeks executing against a target that was never the right one. The Clear Thinking framework calls this the social default: the collective instinct to accept the first definition everyone agrees on and move forward, because solving problems feels productive while defining them feels like stalling. The result is organisations that are perpetually busy and perpetually unimproved -- extinguishing flames that reignite because no one addressed the fire. Define the problem correctly and the solution often becomes obvious. Define it incorrectly and no amount of analytical sophistication will rescue the outcome.
The Framework
The process divides into two distinct phases -- defining the real problem, then exploring the full solution space -- and the single most valuable discipline is keeping them apart.
Phase 1: Define the Problem
The Definition Principle. Take responsibility for defining the problem yourself. Do not let someone else's framing become your framing by default. If you cannot explain the problem to a twelve-year-old without resorting to jargon, you do not yet understand it well enough to make a decision about it.
The Root Cause Principle. Distinguish the disease from the symptoms. The diagnostic question is deceptively simple: "What would have to be true for this problem not to exist in the first place?"
The text illustrates this with Downtown Dog Rescue in Los Angeles, where founder Lori Weise discovered that 30 percent of shelter dogs were owner surrenders -- families who loved their pets but could not afford to feed them. The obvious problem ("how do we get more people to adopt?") was the wrong problem. The root cause was economic hardship among existing owners. Solving for that reduced shelter intake by 75 percent at lower cost than housing the animals.
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.
- 1mo ago First seen · 206 lines · 124 tokens per session scan A 398bdb4b3521
defining-and-exploring-problems is a skill published in the GitHub repository fatihguner/foreman (62 stars, last pushed 1mo ago), licensed MIT. It adds 124 tokens to every session and 4,404 once invoked, about $0.0005 per session on Opus 5.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-09-06.
Other skills, from other repositories
laoyeye
A thinking and learning partner that uses named methods such as questioning, first-principles analysis, comparison, and fact-checking. It can also turn a clear request into teaching material or a structured task.
land
Build a stepped deck an audience works through until one thing of it stays with them. Use when the user needs an audience to come away holding one thing.
toy
Build a world the human drives until how a thing behaves is intuitive. Use when the user needs to hold how something behaves and reading has not made it intuitive.
grasp
Build a walkthrough the user works through until they can pass a quiz on it. Use when the user needs to understand something deeply and be quizzed on it.
learn
Help the user understand something well enough to explain it. Use when the user needs to understand something and it is not yet clear what kind of understanding they need.
multi-perspective-decision-wheel
Structure a decision or design challenge through multiple perspectives before committing to action. Use as a synthesis step after scoping, mapping, and dilemma navigation when a group needs a wiser next step.