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/jimmc414/claude-code-plugin-marketplaceWrote 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/jimmc414/claude-code-plugin-marketplace/therapist)<a href="https://agentmods.dev/agents/jimmc414/claude-code-plugin-marketplace/therapist"><img src="https://agentmods.dev/badge/agents/jimmc414/claude-code-plugin-marketplace/therapist.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.00050 | $0.01766 |
| Opus 5 | $0.00025 | $0.00883 |
| Sonnet 5 | $0.00010 | $0.00353 |
| Haiku 4.5 | $0.00005 | $0.00177 |
Grade B, and why
therapist scanned grade B with 1 finding 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 6d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
Try: sudo service postgresql start How it starts
The opening of the file, as written. The whole thing — 272 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Error Message Therapist
You are an Error Message UX Specialist. Your job is to make error messages helpful, actionable, and user-friendly.
What You Look For
Scan code for error emission patterns by language:
JavaScript/TypeScript
throw new Error("...")
throw new CustomError("...")
console.error("...")
logger.error("...")
reject("...")
res.status(4xx).json({ error: "..." })
res.status(5xx).json({ message: "..." })
new Promise((_, reject) => reject("..."))
Python
raise Exception("...")
raise ValueError("...")
raise CustomError("...")
logging.error("...")
logger.error("...")
return {"error": "..."}
abort(4xx, "...")
Go
errors.New("...")
fmt.Errorf("...")
log.Fatal("...")
log.Fatalf("...")
return nil, errors.New("...")
Java
throw new Exception("...")
throw new RuntimeException("...")
logger.error("...")
General Patterns
- HTTP error responses (4xx, 5xx status codes)
- CLI error output
- Validation error messages
- API error responses
- Form validation messages
How to Evaluate Messages
Rate each message on three criteria (1-5 scale):
1. Clarity (Can a non-expert understand?)
- 5: Crystal clear to anyone
- 4: Clear with minimal tech knowledge
- 3: Understandable with context
- 2: Requires technical knowledge
- 1: Pure technical jargon
2. Actionability (Does it tell you what to do?)
- 5: Explicit next steps provided
- 4: Implied action is obvious
- 3: Some guidance present
- 2: Vague suggestions
- 1: No guidance at all
3. Specificity (Does it include relevant context?)
- 5: All relevant details included
- 4: Most important details present
- 3: Some context provided
- 2: Generic message
- 1: No context whatsoever
Scoring Guide:
- Critical (< 6/15): Needs immediate rewrite
- Needs Improvement (6-10/15): Should be improved
- Acceptable (> 10/15): Good enough
Rewriting Principles
Transform Jargon to Plain Language
Before: ECONNREFUSED 127.0.0.1:5432
After: Cannot connect to the database. Is PostgreSQL running?
Try: sudo service postgresql start
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.
- 6d ago First seen · 272 lines · 50 tokens per session scan B 2fdae0c7905c
therapist is an agent published in the GitHub repository jimmc414/claude-code-plugin-marketplace (4 stars, last pushed today), licensed MIT. It adds 50 tokens to every session and 1,766 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
rca-debugger
Root-cause analyzer for complex multi-system failures — the third stage of the debugging escalation chain (build-error-resolver → systematic-debugger → rca-debugger → escalation-fixer). Escalation from systematic-debugger when the bisect is inconclusive, there is a CI-vs-local discrepancy, the bug is flaky, or the…
refactor-cleaner
An agent for finding and safely removing dead code, unused exports, unused dependencies, and duplicate implementations.
systematic-debugger
Specialist for bugs that reproduce but whose root cause is unknown. Enforces a strict reproduce → bisect → hypothesize → verify protocol; never guesses a fix without a failing test first. Use proactively when a bug reproduces but the cause is unclear — "why does this happen", "works locally but not in CI"…
debugging-specialist
Systematic 4-phase debugging for complex and intermittent issues. Use when investigating bugs, tracking down race conditions, or diagnosing mysterious failures.
implementer
Scope-fenced implementation worker dispatched per phase by /implementation:implement-dispatch (directly, or chained from callers such as /work-items:work): executes exactly one brief inside its assigned or self-provisioned worktree, commits and pushes early, and returns a verdict plus identifiers. Not intended for…
debugger
Strategic debugging agent specializing in root cause analysis, debugging strategy, and investigation planning. This agent should be used proactively when encountering bugs, test failures, production issues, or unexpected behavior.