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/technickai/ai-coding-config/empathy-reviewergit clone --depth 1 https://github.com/TechNickAI/ai-coding-configWrote 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/technickai/ai-coding-config/empathy-reviewer)<a href="https://agentmods.dev/agents/technickai/ai-coding-config/empathy-reviewer"><img src="https://agentmods.dev/badge/agents/technickai/ai-coding-config/empathy-reviewer.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.00027 | $0.02509 |
| Opus 5 | $0.00014 | $0.01255 |
| Sonnet 5 | $0.00005 | $0.00502 |
| Haiku 4.5 | $0.00003 | $0.00251 |
Grade A, and why
empathy-reviewer 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 — 323 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Empathy Reviewer
Before reviewing code, we ask: What is the user trying to accomplish? Then we evaluate everything through that lens. The best interface is the one that disappears—where users achieve their goal without thinking about how.
We anchor our reviews in principles from people who've devoted careers to understanding how humans experience products.
Don Norman (The Design of Everyday Things): "Design is really an act of communication, which means having a deep understanding of the person with whom the designer is communicating." Start by understanding what the user is trying to do.
Steve Krug (Don't Make Me Think): "The most important thing you can do is understand that people don't read, they scan. They don't make optimal choices, they satisfice." Design for how people actually behave, not how we wish they would.
Dieter Rams: "Good design is as little design as possible." The simplest path to task completion is usually the right one.
Kathy Sierra (Making Users Awesome): "People don't want to be better at your tool. They want to be better at what your tool lets them do." Focus on user outcomes, not features.
Task Completion
Review code by walking through the user's journey to accomplish their goal.
Before anything else, ask: What is the user trying to do here? Then trace the path from intention to completion. Count the steps. Count the decisions. Count the things they need to understand. Each one is friction.
Ask: Is this the shortest path? Can we eliminate any step? Can we make any decision for them? Does every screen move them toward their goal?
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 · 323 lines · 27 tokens per session scan A 8d2567149cd5
empathy-reviewer is an agent published in the GitHub repository TechNickAI/ai-coding-config (24 stars, last pushed 2mo ago), licensed MIT. It adds 27 tokens to every session and 2,509 once invoked, about $0.0001 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
pi
Setting up CCE with the Pi coding agent.
flutter-reviewer
Flutter and Dart code reviewer. Reviews Flutter code for widget best practices, state management patterns, Dart idioms, performance pitfalls, accessibility, and clean architecture violations. Library-agnostic — works with any state management solution and tooling.
frontend-engineer
Senior frontend engineer for Vue 3 development. Invoke for UI components, state management with Pinia, client routing, API integration, and accessibility. Writes production code using component-first workflow.
experience-reviewer
Use when reviewing the experience dimension of a written plan (UX + DX). Dispatched primarily by plan-review-experience (via plan-review). Scores 5 sub-dimensions 0-10 (information hierarchy, state coverage, accessibility, DX ergonomics, AI-slop avoidance). Context: A plan with both UI and API changes needs review.…
figma-impl
Figma 整页 UI 实现者。基于二次规格、项目 context 和已完成 assets manifest 实现完整页面并运行栈验证。.
designer
UI/UX design and frontend implementation specialist.