account-research

account-research is a skill for Claude Code from alebgl77/claude-inc. It costs 70 tokens per session (651 once invoked), scanned A, original, MIT.

A research assistant for investigating companies or people and producing sales information from public sources and connected business data.

In plain words
What is it for?
Use it to assess account fit, find recent company signals, map possible buyers and blockers, form evidence-based pain hypotheses, and prepare conversation openers.
Why use it?
It reduces the time spent gathering background, recent developments, likely problems, and relevant contacts before outreach.

Skill for Claude Code

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

Part of the claude-inc plugin — 54 skills, 3 commands, 9 agents shipped together

Good fit Use it to assess account fit, find recent company signals, map possible buyers and blockers, form evidence-based pain hypotheses, and prepare conversation openers.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/alebgl77/claude-inc/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 alebgl77/claude-inc --skill account-research
Clone the repo
git clone --depth 1 https://github.com/alebgl77/claude-inc

Made for: Claude Code.

Or install claude-inc, the plugin that ships this one along with the rest of its 54 skills, 3 commands, 9 agents.

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/alebgl77/claude-inc/account-research/github.svg)](https://agentmods.dev/skills/alebgl77/claude-inc/account-research)
Your own site
<a href="https://agentmods.dev/skills/alebgl77/claude-inc/account-research"><img src="https://agentmods.dev/badge/skills/alebgl77/claude-inc/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/alebgl77/claude-inc/account-research"><img src="https://agentmods.dev/badge/skills/alebgl77/claude-inc/account-research.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 70 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 651 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00070 $0.00651
Opus 5 $0.00035 $0.00326
Sonnet 5 $0.00014 $0.00130
Haiku 4.5 $0.00007 $0.00065

Measured 9d ago against content hash 87ac4bf7d580, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, 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 9d 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 · 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.

Account Research — Prospector

"Know them better than their own website does."

When to use

  • "Research {company} before I contact them"
  • "Who is {name} at {company}?"
  • "Why would {company} buy {my product}?"
  • Always before draft-outreach or call-prep — research is their fuel
  • Works from public web (search + site + LinkedIn-style signals); upgrades with any CRM/enrichment MCP if connected

Workflow

  1. Frame the mission: what does the user sell, and what would make this account a good or bad fit? Write the fit hypothesis first.
  2. Company scan: what they do (in one sentence a human would say), size/stage signals, business model, who their customers are.
  3. Signal sweep: last 90 days — funding, hiring, launches, leadership changes, tech choices, public complaints. Date every signal.
  4. People map: likely buyer, likely champion, likely blocker — with role-based reasoning when names aren't public.
  5. Pain hypotheses: top 3, each tied to an observed signal (not generic industry pains).
  6. Entry angle: the single most credible reason to talk to them THIS month, plus 2 conversation openers in natural language.
  7. Disqualifiers: honest list of reasons to skip this account. Recommendation: pursue / park / drop.

Output format

## Account brief — {company}
Fit hypothesis: {1 line} · Verdict: PURSUE / PARK / DROP

**What they do**: ...
**Signals (dated)**: • {date} — {signal} → {why it matters}
**People**: buyer {role} · champion {role} · blocker {role}
**Top pains (evidence-tied)**: 1. ... 2. ... 3. ...
**Entry angle**: ...
**Openers**: "..." / "..."
**Disqualifiers**: ...

Quality bar

  • Every signal is dated and sourced (link or "observed on their site")
  • Pains reference evidence, not industry clichés
  • The entry angle would survive being read aloud to the prospect
  • A clear verdict — no fence-sitting
  • Under 1 page; a rep can absorb it in 3 minutes

Example

Ask: "Research Maison Verdier (wine e-commerce) for my SEO service." Produced: brief showing recent PrestaShop 9 migration + 2 job posts for marketing, pain hypothesis "traffic lost in migration", entry angle referencing their broken category pages, verdict PURSUE with two openers.

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. 9d ago First seen · 55 lines · 70 tokens per session scan A 87ac4bf7d580

Subscribe to this mod's changes

account-research is a skill published in the GitHub repository alebgl77/claude-inc (14 stars, last pushed today), licensed MIT. It adds 70 tokens to every session and 651 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

mcp-lark

Based on FeiShu(飞书) / Lark's OpenAPI MCP server, manage user information, chats, emails, cloud documents, multidimensional tables, tasks, calendars, etc.

aahl/skills · 45 tokens

giasip-dispatch

A skill for sending a task to other AI models and collecting their results. It supports direct API calls, command-line tools and built-in internal agents, depending on the model.

GiaSip/giasip-skills · 162 tokens

checklist

Activate when: user says 'let's make sure we don't skip anything', 'we need a pre-flight', 'build me a checklist for X', 'we keep missing steps in our deployment / close / launch', 'Gawande / Pronovost / checklist manifesto'. Do NOT activate when: the task is simple and one-off with no recurrence; the user is asking…

deciqAI/knowledge-skills · 105 tokens

deep-work

Activate when: user says 'I can never find time for focused work', 'I feel busy but produce nothing', 'I keep getting interrupted', 'I want to protect my focus time', 'flow state', 'deliberate practice', 'Cal Newport', or asks how to make progress on hard cognitive work (research, writing, engineering, strategy). Do…

deciqAI/knowledge-skills · 123 tokens

dichotomy-of-control

Activate when: user says "I can't stop worrying about something I can't control," "I'm anxious about how this will turn out," "I keep replaying what went wrong," "I need them to change," "this uncertainty is paralyzing me," or is processing a setback, preparing for a high-stakes unknown outcome, or stuck in…

deciqAI/knowledge-skills · 143 tokens

intrinsic-drive

Activate when: user says 'I've lost motivation', 'I'm burning out', 'the excitement is gone', 'I keep starting things but can't sustain them', 'I'm going through the motions', 'I don't know what drives me anymore', or describes a flat feeling after achieving a major goal. Do NOT activate when: person shows signs of…

deciqAI/knowledge-skills · 107 tokens