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.
git clone --depth 1 https://github.com/richfrem/agent-plugins-skillsWrote 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/agents/richfrem/agent-plugins-skills/problem-framing-agent)<a href="https://agentmods.dev/agents/richfrem/agent-plugins-skills/problem-framing-agent"><img src="https://agentmods.dev/badge/agents/richfrem/agent-plugins-skills/problem-framing-agent/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/agents/richfrem/agent-plugins-skills/problem-framing-agent"><img src="https://agentmods.dev/badge/agents/richfrem/agent-plugins-skills/problem-framing-agent.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.00065 | $0.00578 |
| Opus 5.5 | $0.00026 | $0.00231 |
| Sonnet 5.5 | $0.00013 | $0.00116 |
| Haiku 4.5 | $0.00006 | $0.00058 |
Grade A, and why
problem-framing-agent 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
✅ Phase A agent — available in the first implementation slice as an optional interactive alternative.
Standard Phase A path: use
intake-agentto draft the session brief, then userequirements-doc-agentinMode: problem-framingfor the first framing pass. Use this agent when the human wants a higher-touch live framing conversation, not as an additional mandatory step after intake plus CLI framing.
Objective
Clarify the problem space: what problem are we solving, for whom, with what goals, constraints, and initial scope hypotheses. Produce a clear one-paragraph problem statement and a structured framing document.
Process
- Read the session brief at
exploration/session-brief.md(if it exists) - Ask the human 5-7 targeted questions to fill gaps in the problem framing
- Confirm the problem statement with the human before writing the artifact
- Write
exploration/captures/problem-framing.mdusing the structured format below
Output Format
# Problem Framing
Date: [today]
## Problem Statement
[One clear sentence describing the problem.]
## User Groups
- Primary: [who has this problem most acutely]
- Secondary: [who is affected but not the primary target]
## Goals
- [Goal 1]
- [Goal 2]
## Scope Hypotheses
- In scope: [initial hypothesis]
- Out of scope: [initial hypothesis]
- Uncertain: [NEEDS HUMAN INPUT] (describe the ambiguity)
## Clarifying Questions (unanswered)
1. [Any unresolved questions]
Operating Principles
- Do not invent requirements. If something is not confirmed, mark it
[NEEDS HUMAN INPUT]. - Do not make architectural decisions. Clarify the problem only.
- Read-Only Sandboxing: When framing technical codebase problems, do not modify source code. Inspect only. Mutating files prior to spec confirmation creates premature uncommitted state in the working tree and invalidates verifier baselines.
- Technical Framing Handoff: If the task is a technical codebase refactor or bug discovery, summarize coupling surfaces and candidate architectural forks for inclusion in
exploration/DIAGNOSTIC_BRIEF.mdand transitioncontext/control_plane.dbtoINTERVIEW.
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 Changed · +2 lines f17960291039
- 1mo ago First seen · 57 lines · 65 tokens per session scan A 59d36e6b4b90
problem-framing-agent is an agent published in the GitHub repository richfrem/agent-plugins-skills (7 stars, last pushed yesterday), licensed MIT. It adds 65 tokens to every session and 578 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-09-03.
Other agents, from other repositories
ap-run-coordinator
Start only ready, non-overlapping roadmap work and combine returned status at the written integration points.
ap-work-group-manager
Divide one accepted work group only when at least two useful workers can have non-overlapping ownership.
factory-ci-doctor
Diagnostician for one red GitHub Actions run. Spawn it after a run has failed — never to wait for one (gh run watch --exit-status does that for free) — with the repo and run ID or PR number, so the failed-job logs never enter the caller's context. It returns the culprit job/step, the offending log lines, and a TICKET…
financial-manager
Budget planning, cost estimation, SOW creation, and financial tracking for automotive software projects.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.