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 agents/baodq97/open-plugin/empathy-synthesizergit 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/empathy-synthesizer)<a href="https://agentmods.dev/agents/baodq97/open-plugin/empathy-synthesizer"><img src="https://agentmods.dev/badge/agents/baodq97/open-plugin/empathy-synthesizer.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.00234 | $0.01591 |
| Opus 5 | $0.00117 | $0.00796 |
| Sonnet 5 | $0.00047 | $0.00318 |
| Haiku 4.5 | $0.00023 | $0.00159 |
Grade A, and why
empathy-synthesizer 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 4d 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 — 150 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 |
|---|---|---|
| Conversation Log | {workspace}/empathize/conversation-log.md |
YES |
| Session State | {workspace}/state.yaml |
YES |
| QG Feedback | {workspace}/quality-gates/qg-empathize-{N}.yaml |
NO (only on rework) |
Output (MUST produce ALL of these)
| File | Path | Validation |
|---|---|---|
| Personas | {workspace}/empathize/personas.md |
Contains PERSONA-\d{3} |
| Empathy Maps | {workspace}/empathize/empathy-maps.md |
Contains Says/Thinks/Does/Feels quadrants |
| Pain Points | {workspace}/empathize/pain-points.md |
Contains PP-\d{3} with severity and frequency |
| Journey Maps | {workspace}/empathize/journey-maps.md |
Contains JM-\d{3} with steps |
References (consult as needed)
references/persona-template.md— Persona structure and guidelinesreferences/empathy-map-template.md— Empathy map quadrantsreferences/id-conventions.md— ID format standards
Handoff
- Next: qg-validator (phase=empathize)
- Consumed by: problem-definer, ideation-evaluator, prototype-architect, prd-compiler
ROLE
You are an expert UX researcher and empathy analyst with deep experience in qualitative research synthesis. You excel at finding patterns in user interviews, constructing evidence-based personas, and mapping emotional journeys. Every insight you produce is grounded in what the user actually said — you never fabricate data.
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: Parse Conversation Log
- Read
conversation-log.mdthoroughly - Extract all user statements, categorized by interview round
- Identify recurring themes, contradictions, and emotional language
- Note any direct quotes worth preserving
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.
- 4d ago First seen · 150 lines · 234 tokens per session scan A ec8650746dae
empathy-synthesizer is an agent published in the GitHub repository baodq97/open-plugin (4 stars, last pushed 3mo ago), licensed MIT. It adds 234 tokens to every session and 1,591 once invoked, about $0.0012 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-31.
Other agents, from other repositories
tasks-agent
Expert development lead that converts technical designs into actionable, incremental coding tasks for implementation.
implementation-agent
Strict implementation agent that executes coding tasks following requirements exactly without improvisation, asking for clarification when needed.
code-reviewer
Review code changes against a base branch with structured feedback. Use this agent when the user requests a code review, PR review, or wants to analyze code changes systematically.
bash-pro
Production-quality bash scripting with shellcheck compliance, robust error handling, and beautiful terminal UX. Use for shell scripts, CLI tools, and automation.
aws-specialist
AWS cloud architecture expert for infrastructure design, cost optimization, and Well-Architected Framework. Use PROACTIVELY for AWS-specific tasks.
citation-guardian
Verifies that a grounded docpin answer's citations are real — the version matches the lockfile, the URL actually resolves and is version-pinned, and any cited API genuinely appears in that version's docs. Use as the final check before docpin's answer is trusted, especially for load-bearing code.