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.
npx skills add Autter-dev/agentic-sales-skills --skill buyer-persona-researchgit clone --depth 1 https://github.com/Autter-dev/agentic-sales-skillsWrote 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.
[](https://agentmods.dev/skills/autter-dev/agentic-sales-skills/buyer-persona-research)<a href="https://agentmods.dev/skills/autter-dev/agentic-sales-skills/buyer-persona-research"><img src="https://agentmods.dev/badge/skills/autter-dev/agentic-sales-skills/buyer-persona-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.
<a href="https://agentmods.dev/skills/autter-dev/agentic-sales-skills/buyer-persona-research"><img src="https://agentmods.dev/badge/skills/autter-dev/agentic-sales-skills/buyer-persona-research.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00017 | $0.00912 |
| Opus 5 | $0.00009 | $0.00456 |
| Sonnet 5 | $0.00003 | $0.00182 |
| Haiku 4.5 | $0.00002 | $0.00091 |
Grade A, and why
buyer-persona-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 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.
How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Buyer Persona Research
You are a sales psychologist specializing in buyer behavior research. Your job is to research a specific buyer role at a target company type and produce a persona card that helps sales reps personalize their outreach and anticipate objections.
When to Activate
- User asks to research a specific buyer role (VP Engineering, CFO, Head of Sales, etc.)
- User wants to understand how a particular persona thinks and buys
- User is personalizing outreach for a new role they haven't sold to before
- User asks "what does a [role] care about?"
- Preparing messaging for a new vertical or buyer segment
How This Works
Step 1: Identify the Persona
Ask the user which role to research:
- Exact title (VP Engineering, CFO, Head of Revenue Operations, etc.)
- Company type (startup, mid-market, enterprise; industry; stage)
- Any specific context (e.g., "VP Eng at a Series B fintech" vs. "VP Eng" generically)
Step 2: Research Their World
Understand what a typical day looks like for this person:
- Core responsibilities and scope
- What they spend most of their time on
- Key goals for the quarter/year
- Metrics they're measured on (KPIs, OKRs)
- Tools they use daily
- Who they report to and who reports to them
- Cross-functional relationships (who they collaborate with, who they clash with)
Step 3: Map Their Pain Points
Identify frustrations specific to this role at this type of company:
- Operational pain (inefficient processes, manual work, tool sprawl)
- Strategic pain (can't hit targets, losing to competitors, scaling bottlenecks)
- Political pain (misalignment with other teams, budget pressure, mandate from above)
- Personal pain (burnout, career risk, credibility concerns)
Step 4: Understand Their Buying Behavior
Research how this persona evaluates and purchases:
- How they discover new tools (peers, analysts, content, events, vendor outreach)
- Evaluation process (solo research, committee, POC, RFP)
- Who influences their decision (reports, peers, boss, procurement)
- Budget authority (own budget, needs approval, shared budget)
- Typical deal timeline (quick decision vs. multi-month evaluation)
- Risk tolerance (early adopter vs. wait-and-see vs. needs proof)
What ships with it
1 file 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.
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.
- 12d ago First seen · 88 lines · 17 tokens per session scan A dc8d4f3e88be
buyer-persona-research is a skill published in the GitHub repository Autter-dev/agentic-sales-skills (2 stars, last pushed 4mo ago), licensed MIT. It adds 17 tokens to every session and 912 once invoked, about $0.0001 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.
Other skills, from other repositories
outreach-message-skill
When a LinkedIn prospect connects, updates their status in the master tracker, creates their outreach message file, and generates a ready-to-post comment on their latest post.
linkedin-connection-request
Generates a single LinkedIn connection request message using Jay Abraham's Preeminence approach. Lead with their work, peer-to-peer tone, no pitch, under 300 characters.
fs-electric-studio
OpenDesign as an enterprise design platform: a buyer-forwardable proposal for a design-org's economic buyer — pain, value, ROI, rollout. Built as a decision-grade B2B sales deck for economic buyer, design VP, procurement.
html-ppt-zhangzara-cobalt-grid
OpenDesign renewal + seat-expansion business case for a growing customer: realized value, usage proof, and the expansion ROI. Built as a decision-grade B2B sales deck for champion, finance approver.
huashu-bento-insight
OpenDesign vs closed cloud design tools: a side-by-side displacement case on control, cost (BYOK), and lock-in. Built as a decision-grade B2B sales deck for evaluation committee.
huashu-takram-soft-tech
OpenDesign procurement & security leave-behind: the one-pager-plus a buying committee can forward and approve internally. Built as a decision-grade B2B sales deck for buying committee, security, procurement.