resonance-sales-account-intelligence

resonance-sales-account-intelligence is a skill for Claude Code from manusco/resonance. It costs 62 tokens per session (1,520 once invoked), scanned A, original, MIT.

A workflow for ranking customer or prospect accounts by current signals, explaining why each deserves attention, and recommending the next action. An account is a company or organization being evaluated for sales work.

In plain words
What is it for?
Prioritizing new prospects, dormant or churned customers, and active accounts with expansion signals; creating account briefs; preparing customer decks; and reviewing expansion potential.
Why use it?
It helps sales teams focus on evidence of timely opportunity instead of simply choosing the largest companies. It also requires a recent signal and a concrete follow-up for each recommendation.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: installed under .agents/ (shared by several agents); mentions AGENTS.md.

Part of the resonance plugin — 86 skills, 38 commands shipped together

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 skills/manusco/resonance/account-intelligence
Any agent
npx skills add manusco/resonance --skill account-intelligence
Clone the repo
git clone --depth 1 https://github.com/manusco/resonance

Made for: Claude Code.

Or install resonance, the plugin that ships this one along with the rest of its 86 skills, 38 commands.

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 resonance-sales-account-intelligence

README.md
[![agentmods](https://agentmods.dev/badge/skills/manusco/resonance/account-intelligence.svg)](https://agentmods.dev/skills/manusco/resonance/account-intelligence)
Your own site
<a href="https://agentmods.dev/skills/manusco/resonance/account-intelligence"><img src="https://agentmods.dev/badge/skills/manusco/resonance/account-intelligence.svg" alt="Measured on agentmods" height="20"></a>
Per session 62 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,520 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.1 $0.00062 $0.01520
Opus 5 $0.00031 $0.00760
Sonnet 5 $0.00012 $0.00304
Haiku 4.5 $0.00006 $0.00152

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

Security

Grade A, and why

resonance-sales-account-intelligence 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 6d 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.

.agents/skills/sales/account-intelligence/SKILL.md · 101 lines

How it starts

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

/resonance-sales-account-intelligence: know your accounts before you call

Role: resonance-sales Input: An account list, CRM data, usage signals, or a meeting brief request. Output: A ranked account list with why-now evidence and recommended actions, OR a structured account brief/deck. Definition of Done: Every recommended account has a named signal, a recency date, and a concrete next step. No accounts recommended solely because they are large. No fabricated ownership, intent, or titles. Free of AI slop and em dashes. Passed the validator.

Prerequisites (fail fast)

  • An account pool is defined (named accounts, segment, territory, or CRM filter).
  • At least one data source is accessible (CRM records, usage data, public signals, or account notes).

Algorithm

Copy this checklist and tick items as you go.

Job 1: Account Prioritization (Trigger Radar)

  1. Define the Pool: Separate the account pool into three motions:

    • New-logo: Accounts with no existing relationship.
    • Recovery: Churned or dormant accounts with re-engagement potential.
    • Expansion: Active accounts with usage or seat growth signals. → verify: every account is classified into exactly one motion.
  2. Gather Evidence: Pull company-approved evidence first (CRM, usage data, account notes, meeting history). Add public triggers (funding rounds, leadership changes, job postings, tech stack signals) only when internal data is insufficient. → verify: internal evidence is primary, public evidence is supplementary.

  3. Score by Actionability: Rank accounts on four dimensions:

    • Actionability: Can the rep take a concrete next step today?
    • Recency: How recent is the signal? Use absolute dates, never "recently."
    • Fit: Does the account match the ICP on firmographic and behavioral criteria?
    • Next-step clarity: Is the recommended action specific enough for a rep to execute? → verify: each scored account has values on all four dimensions.

Read the full file on GitHub · 101 lines

Files

What ships with it

4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 6d ago First seen · 101 lines · 62 tokens per session scan A c388c2800b05

Subscribe to this mod's changes

resonance-sales-account-intelligence is a skill published in the GitHub repository manusco/resonance (37 stars, last pushed yesterday), licensed MIT. It adds 62 tokens to every session and 1,520 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-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens