agentmods.dev

frame-problem

frame-problem is a command for Claude Code from ThibautBaissac/rails_ai_agents. It costs 70 tokens per session (1,230 once invoked), scanned A, original, MIT.

A command guide for turning a vague feature request into a clearly defined problem and comparing possible solutions. It uses questions such as the “5 Whys” to find the underlying need behind a requested button, screen, or feature.

In plain words
What is it for?
Use it to analyze requests from tickets, emails, Slack messages, or conversations, identify the requester and urgency, uncover the root need, and outline alternative technical approaches.
Why use it?
It helps prevent building the wrong thing when a stakeholder describes a solution before explaining the problem they need solved.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter.

not rated 672repo +1 5mo ago A scan 70 tokens original MIT

Good fit Use it to analyze requests from tickets, emails, Slack messages, or conversations, identify the requester and urgency, uncover the root need, and outline alternative technical approaches.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/thibautbaissac/rails_ai_agents/frame-problem
View source ↗ ThibautBaissac/rails_ai_agents thibautbaissac.github.io
Install

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.

Clone the repo
git clone --depth 1 https://github.com/ThibautBaissac/rails_ai_agents

Made for: Claude Code.

Wrote 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.

agentmods badge for frame-problem

README.md
[![agentmods](https://agentmods.dev/badge/commands/thibautbaissac/rails_ai_agents/frame-problem/github.svg)](https://agentmods.dev/commands/thibautbaissac/rails_ai_agents/frame-problem)
Your own site
<a href="https://agentmods.dev/commands/thibautbaissac/rails_ai_agents/frame-problem"><img src="https://agentmods.dev/badge/commands/thibautbaissac/rails_ai_agents/frame-problem/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.

agentmods 80×15 button for frame-problem

Your own site · 80×15
<a href="https://agentmods.dev/commands/thibautbaissac/rails_ai_agents/frame-problem"><img src="https://agentmods.dev/badge/commands/thibautbaissac/rails_ai_agents/frame-problem.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 70 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,230 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00070 $0.01230
Opus 5.5 $0.00028 $0.00492
Sonnet 5.5 $0.00014 $0.00246
Haiku 4.5 $0.00007 $0.00123

Measured 2mo ago against content hash 8e9198e218a2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

frame-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 2mo 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.

.claude/commands/frame-problem.md · 157 lines

How it starts

The opening of the file, as written. The whole thing — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Problem Framing & Solution Discovery

You are a technical architect helping translate raw stakeholder requests into well-framed problems with optimal solution approaches.

Your Mission

Transform vague or potentially misguided feature requests into clear problem statements with architectural alternatives.

Example transformation:

  • Request: "Add an XLS export button on vendor list"
  • Reframed: "Stakeholder needs visibility into vendor activity. Solutions: (A) Metabase dashboard, (B) Custom reporting UI, (C) SQL chatbot agent"

The Problem Framing Process

Phase 1: Understand the Raw Request

  1. Ask the user to describe the request they received from the stakeholder

    • Accept any format: Slack message, email, verbal request, ticket description
    • Don't judge the request yet - just capture it

  2. Extract the surface-level ask:

    • What feature/button/screen was requested?
    • Who made the request? (role/department)
    • Any mentioned urgency or deadline?

Phase 2: The "5 Whys" Discovery

Ask progressively deeper questions to uncover the root need:

Round 1: Understand the Immediate Problem

  • "What problem is the stakeholder trying to solve?"

    • Context: Making a decision? Tracking something? Fixing a workflow? Compliance?

  • "What do they currently do to accomplish this?"

    • Context: Manual workaround? Existing feature that's inadequate? Nothing?

  • "What triggered this request now?"

    • Context: Specific pain point? Upcoming event? Process change?
Round 2: Identify Success Criteria
  • "What does success look like for them?"
  • "Who else is affected by this problem?"
  • "How often do they need this?" (Daily? Monthly? Ad-hoc?)
Round 3: Explore Constraints & Context
  • "Are there existing features that partially solve this?"
    • Search the codebase with Grep/Glob if needed
  • "What have they tried already?"
  • "What's the actual data they need access to?"

Phase 3: Analyze Existing Codebase

Read the full file on GitHub · 157 lines

Changes

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.

  1. 2mo ago First seen · 157 lines · 70 tokens per session scan A 8e9198e218a2

Subscribe to this mod's changes

frame-problem is a command published in the GitHub repository ThibautBaissac/rails_ai_agents (672 stars, last pushed 5mo ago), licensed MIT. It adds 70 tokens to every session and 1,230 once invoked, about $0.0003 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.

Planning
Related

frame-problem compared with commands from other repositories

frame-problem next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
frame-problemThibautBaissac/rails_ai_agentsCommand6725mo agoMITA70Claude Code
checklistgithub/spec-kitCommand148kyesterdayMITA13Claude Code
clarifygithub/spec-kitCommand148kyesterdayMITA27Claude Code
specifygithub/spec-kitCommand148kyesterdayMITA13Claude Code
analyzegithub/spec-kitCommand148kyesterdayMITA26Claude Code
convergegithub/spec-kitCommand148kyesterdayMITA35Claude Code
implementgithub/spec-kitCommand148kyesterdayMITA14Claude Code