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 itseffi/agentic-os --skill problem-structuringgit clone --depth 1 https://github.com/itseffi/agentic-osWrote 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/itseffi/agentic-os/problem-structuring)<a href="https://agentmods.dev/skills/itseffi/agentic-os/problem-structuring"><img src="https://agentmods.dev/badge/skills/itseffi/agentic-os/problem-structuring/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/itseffi/agentic-os/problem-structuring"><img src="https://agentmods.dev/badge/skills/itseffi/agentic-os/problem-structuring.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.00020 | $0.00315 |
| Opus 5.5 | $0.00008 | $0.00126 |
| Sonnet 5.5 | $0.00004 | $0.00063 |
| Haiku 4.5 | $0.00002 | $0.00032 |
Grade A, and why
problem-structuring 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.
What it actually says
Problem Structuring
Break down complex problems into actionable recommendations.
When to Use
When facing a complex, ambiguous problem that needs structured analysis.
The Process
1. Simplify the Problem
- Identify core components
- List key stakeholders
- Summarize in 2-3 sentences
2. Deductive Analysis (Top-Down)
Start broad, work to specifics:
- What's the general situation?
- Create logical tree of options
- Map cause-and-effect relationships
- Explore branches and outcomes
3. Inductive Analysis (Bottom-Up)
Start with specifics, find patterns:
- Examine data points and examples
- Look for patterns and trends
- What do specifics suggest about the whole?
4. Synthesize
Combine both approaches:
- Where do they agree?
- Where do they conflict?
- What insights emerge?
5. Develop Recommendation
Based on analysis:
- Clear, actionable recommendation
- Rationale tied to analysis
- Trade-offs acknowledged
Output Format
- Simplified problem: Concise summary
- Deductive analysis: Logical tree with options
- Inductive analysis: Patterns from data
- Synthesis: Combined insights
- Recommendation: Clear action with rationale
When Not to Use
Do not use this skill when the request is unrelated, low-stakes, or better handled by a simpler direct response.
What ships with it
1 file 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.
- 1mo ago First seen · 62 lines · 20 tokens per session scan A a9ca5bc40803
problem-structuring is a skill published in the GitHub repository itseffi/agentic-os (117 stars, last pushed 14d ago), licensed MIT. It adds 20 tokens to every session and 315 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
vague-requirement-unpacker
A planning aid for turning a vague business request into questions, a narrowed scenario, and an initial scope outline. It is meant for early alignment before a full PRD, or product requirements document, exists.
reviewcourt
A review tool for completed Tencent Meeting requirements or technical-plan meetings. It turns the meeting notes and transcript into a verdict, such as approved, conditionally approved, rejected, or lacking enough information.
competitive-product-research
A research workflow for comparing products and explaining how they differ. It examines user experience and business strategy, then produces a report in HTML or Markdown with traceable sources.
opc-board
A review skill for testing whether a one-person business, side project, or open-source idea is practical. Five advisers score its logic, ability to be delivered, growth potential, viability, and risks, then give a Go or No-Go result.
pm-requirement-review-simulator
A rehearsal for reviewing a product requirements document, or PRD—a written description of what a product or feature should do. Five cross-functional roles challenge the requirements before the real meeting.
ide-briefing-ppt
Generates a single-file 1280x720 HTML presentation by reusing the frozen Light IDE visual system extracted from LLM Wiki 分享.html. Use only when the user names ide-briefing-ppt, asks to reuse that deck's UI, or explicitly requests the combined light-gray canvas, white panels, amber accent, terminal, and file-tree…