handoff-record-validator

handoff-record-validator is an agent for Claude Code from t0ddc3by/claude-for-customer-success. It costs 156 tokens per session (2,137 once invoked), scanned A, original, no licence file.

A checker for records passed from Sales to Customer Success, the team responsible for helping customers achieve results. It reviews 11 required sections and 4 mandatory fields, then gives a completeness assessment and a 1–5 quality score.

In plain words
What is it for?
Use it to review a new Sales-to-Customer Success handoff and identify missing fields, incomplete sections, or stakeholder blind spots.
Why use it?
It finds missing information and unaddressed stakeholders before the next team relies on the handoff. This reduces gaps when responsibility for a new account changes hands.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: model in frontmatter.

Good fit Use it to review a new Sales-to-Customer Success handoff and identify missing fields, incomplete sections, or stakeholder blind spots.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/t0ddc3by/claude-for-customer-success/handoff-record-validator
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.

Clone the repo
git clone --depth 1 https://github.com/t0ddc3by/claude-for-customer-success

Made for: Claude Code.

Wrote 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.

agentmods badge for handoff-record-validator

README.md
[![agentmods](https://agentmods.dev/badge/agents/t0ddc3by/claude-for-customer-success/handoff-record-validator/github.svg)](https://agentmods.dev/agents/t0ddc3by/claude-for-customer-success/handoff-record-validator)
Your own site
<a href="https://agentmods.dev/agents/t0ddc3by/claude-for-customer-success/handoff-record-validator"><img src="https://agentmods.dev/badge/agents/t0ddc3by/claude-for-customer-success/handoff-record-validator/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.

agentmods 80×15 button for handoff-record-validator

Your own site · 80×15
<a href="https://agentmods.dev/agents/t0ddc3by/claude-for-customer-success/handoff-record-validator"><img src="https://agentmods.dev/badge/agents/t0ddc3by/claude-for-customer-success/handoff-record-validator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 156 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,137 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin unknown 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.1 $0.00156 $0.02137
Opus 5 $0.00078 $0.01069
Sonnet 5 $0.00031 $0.00427
Haiku 4.5 $0.00016 $0.00214

Measured 12d ago against content hash a061687ad8a0, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

handoff-record-validator 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 12d 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.

handoff/agents/handoff-record-validator.md · 173 lines

The source is not reproduced here

A licence we could not identify

The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.

Read it on GitHub

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. 12d ago First seen · 173 lines · 156 tokens per session scan A a061687ad8a0

Subscribe to this mod's changes

handoff-record-validator is an agent published in the GitHub repository t0ddc3by/claude-for-customer-success (61 stars, last pushed 3d ago), with no licence file. It adds 156 tokens to every session and 2,137 once invoked, about $0.0008 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.

Related

Other agents, from other repositories