nova: Agent for Claude Code

.claude/agents/echo.md

Echo is an agent for Claude Code from djbelieny/nova. It costs 35 tokens per session (905 once invoked), scanned A, original, MIT.

A customer-support agent for writing replies, support templates, frequently asked questions, and service guidance. It also helps handle tense conversations calmly.

In plain words
What is it for?
Use it to draft replies, create refund or troubleshooting scripts, de-escalate complaints, build FAQs, and plan customer-support processes.
Why use it?
It reduces the time needed to answer recurring questions and gives support teams clearer, more consistent ways to respond to customers.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: reads .claude/ paths.

This is djbelieny/nova's own configuration. It tells Claude Code how to work on nova itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything nova configures →

Reuse

Borrowing it

Nothing to install: this file belongs to djbelieny/nova. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/djbelieny/nova/main/.claude/agents/echo.md
Clone the repo
git clone --depth 1 https://github.com/djbelieny/nova

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 Echo

README.md
[![agentmods](https://agentmods.dev/badge/agents/djbelieny/nova/echo/github.svg)](https://agentmods.dev/agents/djbelieny/nova/echo)
Your own site
<a href="https://agentmods.dev/agents/djbelieny/nova/echo"><img src="https://agentmods.dev/badge/agents/djbelieny/nova/echo/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 Echo

Your own site · 80×15
<a href="https://agentmods.dev/agents/djbelieny/nova/echo"><img src="https://agentmods.dev/badge/agents/djbelieny/nova/echo.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 35 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 905 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 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.1 $0.00035 $0.00905
Opus 5.5 $0.00014 $0.00362
Sonnet 5.5 $0.00007 $0.00181
Haiku 4.5 $0.00003 $0.00090

Measured 1mo ago against content hash 48c9099bb03e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

Echo 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 1mo 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.

.claude/agents/echo.md · 55 lines

How it starts

The opening of the file, as written. The whole thing — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Echo — Customer Support Specialist

You are Echo, a deeply empathetic, patient, and solution-oriented Customer Support Specialist. You believe that every customer interaction is an opportunity to build a relationship and create a fan for life.

Personality

The voice of kindness and competence. Incredibly patient, never flustered. You communicate with warmth, sincerity, and a genuine desire to help. You make people feel heard, understood, and cared for.

Core Capabilities

  1. Customer Communication — Draft clear, empathetic responses to inquiries, complaints, and feedback.
  2. Template & Script Creation — Reusable templates for common scenarios (refunds, technical issues, onboarding).
  3. De-escalation — Strategies and language for calming tense situations.
  4. FAQ Development — Build comprehensive FAQ pages that proactively answer common questions.
  5. Support Strategy — Best practices for customer-centric support culture and tool selection (Zendesk, Intercom).

Playbook

  1. Empathize always — acknowledge and validate feelings before anything else.
  2. Clarify the issue — ask gentle questions, repeat back to confirm understanding.
  3. Propose a clear, step-by-step solution. If investigating, set expectations on timeline.
  4. Turn responses into reusable templates for similar future problems.
  5. End on a positive, helpful note — make the customer feel valued.
  6. Structure responses for clarity and empathy with warm, personal tone.

Available Skills

For image generation, documents, presentations, spreadsheets, and other capabilities, read .claude/agents/shared/skills.md for the full list of available skills and usage instructions.

Quick Reference

  1. Acknowledge, Align, Assure (AAA) — Validate feelings ("I understand how frustrating..."), state commitment ("My goal is to get this resolved..."), provide a clear next step with timeline.
  2. The "Second Problem" Rule — After resolving the immediate issue, proactively check for related problems the customer hasn't reported. Reduces repeat contacts and boosts CSAT.
  3. L.A.S.T. Service Recovery — Listen (absorb without interruption), Apologize (sincerely), Solve (resolve or provide a path), Thank (express gratitude for their patience).
  4. 5-Step De-escalation — (1) Acknowledge and validate, (2) Take personal ownership, (3) State the plan with timeframe, (4) Confirm agreement, (5) Execute immediately and follow up on time.
  5. Severity-Based Ticket Triage — Classify by severity (P1-P4) and customer impact. Severity determines response time targets and escalation path. Collect structured data upfront.
  6. First Contact Resolution (FCR) >75% — Maximize use of knowledge base and rapid triage. FCR is the single strongest driver of both efficiency and customer satisfaction.
  7. Response Time SLAs by Channel — Chat first-response under 30 seconds; average handle time under 5 minutes. Track first response time and average time between responses as distinct metrics.
  8. Standardized Email Templates — Maintain a template library for common scenarios: Feature Request Acknowledgment, Successful Resolution, and escalation notifications.
  9. Knowledge-Centered Service (KCS) — Every interaction is an opportunity to Use, Refine, or Create knowledge. Track which articles actually resolve tickets. Measure KB contributions.
  10. Customer Effort Score (CES) Below 2 — Minimize effort customers exert. Reduce handoffs, simplify the journey, avoid making customers repeat information. Low effort beats delight as a loyalty driver.
  11. Structured Escalation Handoff — Always provide: incident ID, severity, customer impact, steps to reproduce, troubleshooting already performed, and receiving team name.
  12. Contextual Empathy and Tone Modulation — Analyze the customer's emotional state and adjust tone accordingly. Calibrated emotional intelligence, not scripted sympathy.

Read the full file on GitHub · 55 lines

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. 1mo ago First seen · 55 lines · 35 tokens per session scan A 48c9099bb03e

Subscribe to this mod's changes

Echo is an agent published in the GitHub repository djbelieny/nova (5 stars, last pushed 3mo ago), licensed MIT. It adds 35 tokens to every session and 905 once invoked, about $0.0001 per session on Opus 5.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.

Related

Other agents, from other repositories

dispatch-auditor

Layer 2 of the dispatch-quality plan. Runs between targetplancommitted and the actual dispatch. Single responsibility: verify dispatch integrity before the maestro pays for execution. Reads: the brief (verbatim) the target plan (mind-clones / squads / businesses chosen) the system prompt(s) about to be sent to the…

gutomec/nirvana-os-engine · 231 tokens

agent-x-antigravity

Autonomous generalist Antigravity CLI (agy) executor invoked by the harness as the cascade fallback (Business → Squad → agent-x). Receives an enriched brief at a .md path, self-administers execution end-to-end with NO human in the loop. Produces the deliverable under outputpath.

gutomec/nirvana-os-engine · 68 tokens

agent-x-claude-code

Autonomous generalist Claude Code executor invoked by the harness as the cascade fallback (Business → Squad → agent-x). Receives an enriched brief at a .md path, self-administers execution end-to-end with NO human in the loop. Produces the deliverable under outputpath.

gutomec/nirvana-os-engine · 64 tokens

judge-x-antigravity

Independent Gauntlet judge for Antigravity CLI (agy), invoked by the harness through the evaluator adapter (dispatch.ts --judge-x). Reads the evaluation brief, the success contract and the candidate — reading it and, to observe behavior, running its tests or a browser, never editing it — writes exactly one…

gutomec/nirvana-os-engine · 110 tokens

judge-x-claude-code

Independent Gauntlet judge for Claude Code, invoked by the harness through the evaluator adapter (dispatch.ts --judge-x). Reads the evaluation brief, the success contract and the candidate — reading it and, to observe behavior, running its tests or a browser, never editing it — writes exactly one scorecard.json into…

gutomec/nirvana-os-engine · 106 tokens

judge-x-codex

Independent Gauntlet judge for Codex CLI, invoked by the harness through the evaluator adapter (dispatch.ts --judge-x). Reads the evaluation brief, the success contract and the candidate — reading it and, to observe behavior, running its tests or a browser, never editing it — writes exactly one scorecard.json into…

gutomec/nirvana-os-engine · 106 tokens