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/EngDawood/emdash-claude-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/engdawood/emdash-claude-plugin/diagnose)<a href="https://agentmods.dev/agents/engdawood/emdash-claude-plugin/diagnose"><img src="https://agentmods.dev/badge/agents/engdawood/emdash-claude-plugin/diagnose/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/engdawood/emdash-claude-plugin/diagnose"><img src="https://agentmods.dev/badge/agents/engdawood/emdash-claude-plugin/diagnose.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.00029 | $0.01658 |
| Opus 5.5 | $0.00012 | $0.00663 |
| Sonnet 5.5 | $0.00006 | $0.00332 |
| Haiku 4.5 | $0.00003 | $0.00166 |
Grade A, and why
diagnose scanned grade A 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 2mo 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- No `curl` to arbitrary external hosts. The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 2mo ago First seen · 62 lines · 29 tokens per session scan A bc68709b9f3d
diagnose is an agent published in the GitHub repository EngDawood/emdash-claude-plugin (4 stars, last pushed 7d ago), with no licence file. It adds 29 tokens to every session and 1,658 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
diagnostician
Specialized root cause debugger. Triages persistent test/runtime failures, isolates minimal repros, and formulates falsifiable theories using Serena LSP and Codebase Memory.
debugger
Bug investigation specialist. MUST BE USED for bug reports, unexpected behavior, error diagnosis. PROACTIVELY performs systematic root cause analysis using progressive debugging techniques.
fixer
Bug fixer agent. Picks up open GitHub issues labeled 'bug' or 'seeker', creates a fix branch, implements the fix, runs tests, and raises a PR. Use for automated bug fixing from issue queue.
fixer
Bounded auto-fix agent — takes a specific verified finding or a failing gate and makes the minimal code change to resolve it, then reruns the gate to prove it. Use to close a confirmed reviewer/gatekeeper finding. Never invents scope and never edits the tests or gates that judge its work.
debugger
GSD-Lite debugger, dispatched by the GSD orchestrator after repeated executor failures on one task — finds the root cause and returns the debugger result JSON (rootcause, fixdirection) without editing code. Not for general debugging outside a GSD project.
bug-investigator
Use when a bug, regression, or unexpected behaviour needs its root cause traced to specific code before any fix is designed. Investigates only — never edits files. Returns a structured report citing file:line evidence.