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 claude-world/director-mode-lite --skill focus-problemgit clone --depth 1 https://github.com/claude-world/director-mode-liteWrote 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/claude-world/director-mode-lite/focus-problem)<a href="https://agentmods.dev/skills/claude-world/director-mode-lite/focus-problem"><img src="https://agentmods.dev/badge/skills/claude-world/director-mode-lite/focus-problem.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.00056 | $0.00606 |
| Opus 5 | $0.00028 | $0.00303 |
| Sonnet 5 | $0.00011 | $0.00121 |
| Haiku 4.5 | $0.00006 | $0.00061 |
Grade A, and why
focus-problem 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 2d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Focus Problem Analysis
Analyze: $ARGUMENTS
Explore Codebase First
Before diving in, use the Explore agent to understand the context:
Before dispatch, preserve the bounded exploration question and expected result.
If Claude's Agent tool is unavailable or withheld, or Codex's spawn_agent
interface is unavailable or withheld, the maximum depth is reached, or a
concurrency limit rejects the call, do not retry or invent exploration
findings. Return an incomplete dispatch_request and do not advance the plan.
Choose exactly one provider-native form:
- Claude Code:
Agent(subagent_type="Explore", model="haiku", prompt="<bounded prompt>") - Codex CLI:
spawn_agent(agent_type="explorer", task_name="focus_problem", message="<bounded prompt>")
Agent(subagent_type="Explore", model="haiku", prompt="""
Explore the codebase for: $ARGUMENTS (thoroughness: medium)
Focus on:
1. Relevant files and modules
2. Existing similar features
3. Test patterns
4. Architecture patterns
""")
In Codex, send the same exploration request through spawn_agent(...); do not
invoke the Claude example as a second dispatch.
Analysis Framework
1. Core Problem Identification
- What is the real problem?
- Why does it need to be solved?
- What happens if we don't solve it?
2. Minimal Solution Scope
- What's the minimum change needed?
- Which features are essential?
- What can be deferred or omitted?
3. Solution Evaluation
- Option A (Simplest):
- Option B (Balanced):
- Option C (Complete):
- Recommendation: Choose the simplest viable option
4. Implementation Plan
- Step 1: Write tests
- Step 2: Minimal implementation
- Step 3: Update documentation
- Step 4: Commit changes
Output Template
## Problem Definition
### Summary
[One sentence description]
### User Need
[Who needs this? What do they want to achieve?]
### Success Criteria
[How do we know it's done?]
### Scope
- In scope: [List]
- Out of scope: [List]
### Affected Files
- [file1.ts] - [why]
- [file2.ts] - [why]
### Risk Assessment
- [Potential risks and mitigations]
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.
- 2d ago Changed · +14 lines 3cbb661bba4b
- 7d ago First seen · 79 lines · 56 tokens per session scan A e1b5e65bfe44
focus-problem is a skill published in the GitHub repository claude-world/director-mode-lite (81 stars, last pushed 6d ago), licensed MIT. It adds 56 tokens to every session and 606 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
concise
Concise communication mode. Cuts 60-70% of output tokens while keeping natural, readable English. Drops filler, hedging, and pleasantries but maintains grammar and sentence flow. Elaborate on request -- ask for detail and get it, then auto-return to concise. Use when user says "concise mode", "be concise", "less…
peekaboo
Provides runtime observation and interaction for native macOS interfaces through accessibility state and screenshots. Use when the task depends on visible or interactive state in a running SwiftUI/AppKit app: what is rendered, focused, selected, enabled, reachable through menus/windows/dialogs, or experienced across a…
mobile-flows-maestro
This skill should be used when Maestro is explicitly requested or already present and the task is to author, run, or debug iOS/Android Maestro flows; use Maestro MCP; or handle Maestro selectors, system UI, permissions, Keychain, JavaScript, waits, device state, flakiness, or CI. Evidence includes a .maestro directory…
validate-mobile
Run a Maestro flow on an explicitly selected iOS or Android device and report behavioral evidence.
validate-api
Run the project's Hurl scenarios with an OIDC access token passed as a secret variable.
kanso-audit
Use when the user asks for a code review, audit, pre-PR check, quality sweep, or pattern analysis of a diff, branch, module, or codebase. Also use when the user asks to "check" or "look over" their code for issues.