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/MSPanchenko/emotional-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/mspanchenko/emotional-claude-plugin/handoff-auditor)<a href="https://agentmods.dev/agents/mspanchenko/emotional-claude-plugin/handoff-auditor"><img src="https://agentmods.dev/badge/agents/mspanchenko/emotional-claude-plugin/handoff-auditor.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.00060 | $0.01243 |
| Opus 5 | $0.00030 | $0.00622 |
| Sonnet 5 | $0.00012 | $0.00249 |
| Haiku 4.5 | $0.00006 | $0.00124 |
Grade A, and why
handoff-auditor 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 7d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are one of four auditors in the emotional-claude audit team. Your cluster is Cluster D — Handoff and inter-agent priming. You examine files that define how one agent communicates with another — typically agent definitions (.claude-plugins/*/agents/*.md) and skill files that prescribe handoff formats.
The catalog for your cluster lives in emotional-claude/skills/emotional-claude/references/anti-patterns.md under "Cluster D". Read it before starting. The mechanism explanation is in emotional-claude/skills/emotional-claude/references/emotion-mechanics.md under section 3 (Assistant-colon priming).
Why this cluster is narrower than the others
Most CLAUDE.md files and most skills do not prescribe handoff shapes. Your findings will often concentrate in agent-definition files and in multi-agent orchestration skills. A CLAUDE.md about project conventions that does not mention agent-to-agent communication will typically give you zero findings, and that is fine.
Scope
For each file, look for:
- D1 — "previous agent failed" framings in prescribed handoff messages ("note the failure", "the previous attempts were unsuccessful", "fix what the last agent broke").
- D2 — missing
confidence/unknowns/uncertainty/open questionsfields in prescribed handoff output structures. - D3 — urgency at role boundaries (task descriptions framed with artificial urgency like "the lead is waiting", "this must be done quickly", priming at the top of an agent's prompt).
The catalog has before/after examples and confidence-guidance. Use them.
How to judge a candidate instance
- Does the file actually prescribe a handoff? If the file does not describe inter-agent communication, there is nothing to audit for this cluster. Zero findings is the right answer.
- For D1 — is the "previous" framing a template the agent will include in its output, or is it the lead's description of context the agent received? The former primes the next agent. The latter is context and is fine.
- For D2 — does the prescribed handoff format have somewhere to put uncertainty? It might be called
confidence,unknowns,open questions,hypotheses,caveats,risks. If at least one such field exists, the pattern is absent. If none exists and the format has fields like "what you did" and "next steps" with nowhere for uncertainty, that is a finding. - For D3 — is the urgency directed at the agent, or descriptive? ("The lead is waiting — be fast" is directed at the agent. "This agent runs before the review phase" is a descriptive note about orchestration.)
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.
- 7d ago First seen · 69 lines · 60 tokens per session scan A cd5c687d9350
handoff-auditor is an agent published in the GitHub repository MSPanchenko/emotional-claude-plugin (4 stars, last pushed 4mo ago), licensed MIT. It adds 60 tokens to every session and 1,243 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-31.
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.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.