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 agentmods add skills/jabrena/plinth/021-problem-framingnpx skills add jabrena/plinth --skill 021-problem-framinggit clone --depth 1 https://github.com/jabrena/plinthWrote 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/jabrena/plinth/021-problem-framing)<a href="https://agentmods.dev/skills/jabrena/plinth/021-problem-framing"><img src="https://agentmods.dev/badge/skills/jabrena/plinth/021-problem-framing.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 | $0.00082 | $0.00712 |
| Opus 5 | $0.00041 | $0.00356 |
| Sonnet 5 | $0.00016 | $0.00142 |
| Haiku 4.5 | $0.00008 | $0.00071 |
Grade A, and why
021-problem-framing 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 5d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Problem Framing
Guide production of a Problem statement, Current state, Desired state, Stakeholders, and Success criteria for a problem or issue under exploration. This is an interactive SKILL.
What is covered in this Skill?
- Stating the problem independently of any specific solution
- Describing the current state using observable facts
- Describing the desired state as an outcome, not an implementation mechanism
- Identifying stakeholders affected by, accountable for, or informed about the problem
- Defining success criteria that make problem resolution verifiable
- Feeding a clarified problem frame into
022-root-cause-analysisand the remaining Functional Specification lenses
Constraints
Frame the problem before any deeper analysis. When this technique is orchestrated by another workflow, the orchestrator owns clarifying-question sequencing; when applied standalone, ask directly.
- MUST read
references/021-problem-framing.mdbefore applying Problem Framing guidance - MUST state the problem independently of any specific solution, technology, or implementation
- MUST describe the current state using observable facts, not opinions or assumed causes
- MUST describe the desired state as an outcome or capability, not a specific mechanism
- MUST identify stakeholders affected by, accountable for, or informed about the problem, not only the requester
- MUST define success criteria that are observable or measurable
- MUST NOT invent a problem statement, state, stakeholder, or success criterion when the available content is vague or ambiguous; flag the gap for a clarifying question instead
When to use this skill
- Frame this problem before deeper analysis
- Apply problem framing to this issue
- Establish the problem statement, current state, and desired state
- Identify stakeholders and success criteria for this problem
- Draft the Problem Framing section of a Functional Specification
Workflow
- Read the Reference
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.
- 5d ago First seen · 67 lines · 82 tokens per session scan A bf0bc48a1999
021-problem-framing is a skill published in the GitHub repository jabrena/plinth (435 stars, last pushed today), licensed Apache-2.0. It adds 82 tokens to every session and 712 once invoked, about $0.0004 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
session-deep-dive
Deep qualitative analysis of high-signal sessions. Spawns subagents with v2 template, synthesizes patterns, compares against known findings. Use after /session-scan.
brainstorm
Brainstorm Elixir/Phoenix features — explore ideas, compare approaches, gather requirements. Use when vague idea, not sure how to approach, or want to discuss before plan.
ecto-patterns
Ecto patterns — schemas, changesets, queries, migrations, Multi, associations, preloads, upserts. Use when editing Repo calls, Ecto.Query, or schema fields. Skip for Ash.
pseudocode-to-java-code
Converts pseudocode descriptions and algorithm specifications into complete, executable Java code. Use this skill when you need to implement algorithms from pseudocode, translate algorithm descriptions to Java, generate Java code from specifications, convert textbook algorithms to working code, or create executable…
component-family-consistency
Buttons, inputs, pills, badges, calendars, and other interactive components form a visual family — they share the same border-radius, colour logic, shadow scale, border style, and spacing rhythm. Inconsistency between them breaks the sense of a coherent product. Use when building or reviewing a component library…
brand-visual-language
A brand's visual tone — playful or serious, rounded or angular — should be consistent across all UI elements. Shape language in typography, border-radius, and iconography communicates personality before a single word is read. Use when establishing a design system, choosing icon libraries, setting border-radius tokens…