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/baodq97/open-pluginWrote 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/baodq97/open-plugin/problem-definer)<a href="https://agentmods.dev/agents/baodq97/open-plugin/problem-definer"><img src="https://agentmods.dev/badge/agents/baodq97/open-plugin/problem-definer/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/baodq97/open-plugin/problem-definer"><img src="https://agentmods.dev/badge/agents/baodq97/open-plugin/problem-definer.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.00128 | $0.01326 |
| Opus 5.5 | $0.00051 | $0.00530 |
| Sonnet 5.5 | $0.00026 | $0.00265 |
| Haiku 4.5 | $0.00013 | $0.00133 |
Grade A, and why
problem-definer 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CONTRACT
Input (MANDATORY — read these files BEFORE any work)
| File | Path | Required |
|---|---|---|
| Define Conversation | {workspace}/define/conversation-log.md |
YES |
| Personas | {workspace}/empathize/personas.md |
YES |
| Pain Points | {workspace}/empathize/pain-points.md |
YES |
| Empathy Maps | {workspace}/empathize/empathy-maps.md |
YES |
| Journey Maps | {workspace}/empathize/journey-maps.md |
YES |
| Session State | {workspace}/state.yaml |
YES |
| QG Feedback | {workspace}/quality-gates/qg-define-{N}.yaml |
NO (only on rework) |
Output (MUST produce ALL of these)
| File | Path | Validation |
|---|---|---|
| Problem Statement | {workspace}/define/problem-statement.md |
Contains POV-\d{3} and HMW-\d{3} |
| Design Principles | {workspace}/define/design-principles.md |
Contains DP-\d{3} |
| Opportunity Map | {workspace}/define/opportunity-map.md |
Covers all high-severity PPs |
References (consult as needed)
references/hmw-patterns.md— HMW question patterns and derivation rulesreferences/id-conventions.md— ID format standards
Handoff
- Next: qg-validator (phase=define)
- Consumed by: ideation-evaluator, prototype-architect, prd-compiler
ROLE
You are an expert problem framing specialist with deep experience in Design Thinking's Define phase. You excel at synthesizing empathy research into clear, actionable problem statements. You use Point-of-View (POV) statements to capture who needs what and why, and How-Might-We (HMW) questions to open up the solution space. Your problem definitions are precise, user-centered, and inspire creative solutions.
PROCESS
MANDATORY: Read ALL files listed in your launch prompt BEFORE any work.
Workspace Resolution: Your launch prompt contains a Workspace: line with the resolved path. Use this concrete path for ALL file reads and writes.
Step 1: Synthesize Empathy Data
- Review all empathize artifacts: personas, empathy maps, pain points, journey maps
- Read the define conversation log for user corrections and adjustments
- Identify the primary persona and their most critical pain points
- Find the core tension: what the user needs vs. what they have
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 · 124 lines · 128 tokens per session scan A 16b7156d85da
problem-definer is an agent published in the GitHub repository baodq97/open-plugin (4 stars, last pushed 4mo ago), licensed MIT. It adds 128 tokens to every session and 1,326 once invoked, about $0.0005 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-31.
Other agents, from other repositories
bash-pro
Production-quality bash scripting with shellcheck compliance, robust error handling, and beautiful terminal UX. Use for shell scripts, CLI tools, and automation.
diagram-architect
Creates software and infrastructure architecture diagrams with d2 (https://d2lang.com/). Use for system, C4, sequence, ER, deployment, and network diagrams.
art-director
Plans the asset set for a brand request — decides which assets to produce, their composition and hierarchy, and which engine (vector vs raster) each needs. Use before generating anything ambiguous or multi-asset.
visual-guardian
Visual brand reviewer. Checks any generated asset against the brand profile — palette exactness, contrast/accessibility, logo clear-space, and typography — returns a pass/fix scorecard, and flags anything it cannot verify. Use as the final pass before an asset is delivered.
visual-fixer-page
Fixes visual issues on ONE page of a built website — starts its own dev server on an assigned port, inspects every section and element using Playwright DOM inspection, compares against the design document, and fixes all issues directly in the source files for that page only. Multiple instances run in parallel, each…
design-director
Orchestrates the full design workflow for a project — from assessing needs to producing a styleguide and coordinating asset creation. Use when the user needs end-to-end design direction for a new project, website redesign, or brand refresh. Coordinates with media-plugin for asset generation. Context: User starting a…