mdr-analyze

A command for analysing the performance of message delivery, such as whether messages are sent and received as expected.

In plain words
What is it for?
Investigating sent-message delivery performance through the messaging-performance-analyzer skill.
Why use it?
It routes delivery-performance questions to the relevant analysis process instead of treating them as general coding tasks.

Command

Install

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.

agentmods
npx agentmods add commands/sentdm/sent-plugin/mdr-analyze
Clone the repo
git clone --depth 1 https://github.com/sentdm/sent-plugin
Per session 6 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 32 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00006 $0.00032
Opus 5 $0.00003 $0.00016
Sonnet 5 $0.00001 $0.00006
Haiku 4.5 $0.00001 $0.00003

Measured 2d ago against content hash 51d089c0df08, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

mdr-analyze 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 2d 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.

adapter-sources/claude/commands/mdr-analyze.md · 8 lines

What it actually says

Invoke the messaging-performance-analyzer skill with the user's request unchanged:

$ARGUMENTS

Changes

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.

  1. 2d ago First seen · 8 lines · 6 tokens per session scan A 51d089c0df08

Subscribe to this mod's changes

mdr-analyze is a command published in the GitHub repository sentdm/sent-plugin (52 stars, last pushed 23d ago), licensed MIT. It adds 6 tokens to every session and 32 once invoked, about $0.0000 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.