account-research

account-research is a skill for Claude Code from Doris-Labs/sales-skills. It costs 75 tokens per session (1,576 once invoked), scanned A, original, MIT.

A one-page summary of a company, including its business, recent changes, likely decision-makers, and possible problems to investigate.

In plain words
What is it for?
It helps prepare for first meetings, outbound outreach, inbound demos, and expansion conversations.
Why use it?
It reduces time spent collecting basic facts during a call and gives you informed assumptions to test with the account.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the sales-skills plugin — 30 skills shipped together

Good fit It helps prepare for first meetings, outbound outreach, inbound demos, and expansion conversations.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/doris-labs/sales-skills/account-research
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.

Any agent
npx skills add Doris-Labs/sales-skills --skill account-research
Clone the repo
git clone --depth 1 https://github.com/Doris-Labs/sales-skills

Made for: Claude Code.

Or install sales-skills, the plugin that ships this one along with the rest of its 30 skills.

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 account-research

README.md
[![agentmods](https://agentmods.dev/badge/skills/doris-labs/sales-skills/account-research/github.svg)](https://agentmods.dev/skills/doris-labs/sales-skills/account-research)
Your own site
<a href="https://agentmods.dev/skills/doris-labs/sales-skills/account-research"><img src="https://agentmods.dev/badge/skills/doris-labs/sales-skills/account-research/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 account-research

Your own site · 80×15
<a href="https://agentmods.dev/skills/doris-labs/sales-skills/account-research"><img src="https://agentmods.dev/badge/skills/doris-labs/sales-skills/account-research.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 75 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,576 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.00075 $0.01576
Opus 5 $0.00037 $0.00788
Sonnet 5 $0.00015 $0.00315
Haiku 4.5 $0.00007 $0.00158

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

Security

Grade A, and why

account-research 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 11d 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.

skills/account-research/SKILL.md · 141 lines

How it starts

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

Account Research

Purpose

Walk into the call already knowing who they are, what changed recently, who's likely in the room, and what you'll bet is hurting them — so the call is spent testing hypotheses, not gathering facts you could have found beforehand.

Inputs

  • Company name and/or domain
  • Any prior relationship (past deals, contacts, meetings) if it exists
  • Your product and the pains it removes (so research maps to value)
  • The call type and goal (first outbound, inbound demo, expansion)

Method

Work the five blocks below, then collapse them into the one-page brief. Skip nothing — a missing block is a blind spot you'll discover live on the call.

1. Firmographics (the baseline).

  • Industry / sub-vertical, what they actually sell, and to whom
  • Headcount + growth trend (flat, hiring hard, RIF'd recently)
  • Revenue band / funding stage, ownership (PE, VC, public, bootstrapped)
  • HQ + key locations, and whether they're multi-entity
  • Tech stack signals relevant to you (e.g. CRM, CI, comms tools)

2. Recent triggers (the "why now"). Hunt for events in the last ~6 months:

  • Funding round, M&A, or new market entry → budget + change appetite
  • Leadership change (new VP/C-level in your buyer function) → new mandate, fresh eval
  • Aggressive hiring in the function you sell to → scaling pain
  • Product launch, repricing, or strategy pivot → operational strain
  • Press, earnings commentary, layoffs, or regulatory pressure → priorities shifting Each trigger becomes a line you can open the call with.

3. Org structure & likely buying committee. Map the roles, not just names:

Role Who (name/title) Likely stance
Economic buyer owns the budget
Champion feels the pain, will sell internally
Technical/eval judges fit
Blocker status-quo or competing priority
Coach gives you inside info
Flag the gaps — an unknown economic buyer is the single highest-value thing to learn.

Read the full file on GitHub · 141 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. 11d ago First seen · 141 lines · 75 tokens per session scan A c6ea8af63939

Subscribe to this mod's changes

account-research is a skill published in the GitHub repository Doris-Labs/sales-skills (3 stars, last pushed 3mo ago), licensed MIT. It adds 75 tokens to every session and 1,576 once invoked, about $0.0004 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.