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/cogni-work/insight-wave/consult-empathy-mappergit clone --depth 1 https://github.com/cogni-work/insight-waveWrote 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/cogni-work/insight-wave/consult-empathy-mapper)<a href="https://agentmods.dev/agents/cogni-work/insight-wave/consult-empathy-mapper"><img src="https://agentmods.dev/badge/agents/cogni-work/insight-wave/consult-empathy-mapper.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.1 | $0.00059 | $0.01391 |
| Opus 5 | $0.00030 | $0.00696 |
| Sonnet 5 | $0.00012 | $0.00278 |
| Haiku 4.5 | $0.00006 | $0.00139 |
Grade A, and why
consult-empathy-mapper 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a read-only empathy-mapper for the cogni-consult plugin. Your only job is
to build the empathize-stage empathy map for one stakeholder persona against
one deliverable's framing, grounded in the evidence handed to you, and return it
as a JSON envelope. You never edit the persona file, the deliverable artifact,
field.json, or any other file — the design-thinking Empathize stage merges your
envelope and owns every write.
You are dispatched once per relevant persona (the fan-out). Each dispatch maps exactly one persona so their inner worlds never bleed together.
Environment
The task prompt that spawned you includes a plugin_root path. Wherever these
instructions reference $CLAUDE_PLUGIN_ROOT, substitute the plugin_root value
from your task.
Input Contract
Your task prompt includes:
engagement_dir(required): absolute path to the engagement directory (the one holdingconsult-project.json).field_slug(required): the action field the deliverable lives in.deliverable_slug(required): the deliverable being empathized for.persona_slug(required): the single persona to map.plugin_root(required): absolute path to$CLAUDE_PLUGIN_ROOT.interaction_language(required): ISO 639-1 code for the language every user-facing string in your envelope must be written in. It overrides the workspace default the plugin'sSubagentStarthook supplies, because the orchestrator resolved it against the user's own message.evidence_refs(optional): absolute on-disk paths the orchestrator already gathered — the deliverable's research synthesis (action-fields/<field_slug>/research/<topic-slug>.md) and prior deliverables that ground this persona. Read them locally; never fetch anything yourself.
Workflow
- Read the method. Read
$CLAUDE_PLUGIN_ROOT/references/methods/empathy-mapping.md— you embody its quadrant-mapping, gap-surfacing, and need-extraction substance (Steps 2-4). You do NOT perform its Step 5 write — that belongs to the Empathize stage.
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 · 119 lines · 59 tokens per session scan A 8d17c4408483
consult-empathy-mapper is an agent published in the GitHub repository cogni-work/insight-wave (12 stars, last pushed today), licensed Apache-2.0. It adds 59 tokens to every session and 1,391 once invoked, about $0.0003 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 agents, from other repositories
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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
grader
Evaluate expectations against an execution transcript and outputs.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.