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 Doris-Labs/sales-skills --skill stakeholder-mappinggit clone --depth 1 https://github.com/Doris-Labs/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/doris-labs/sales-skills/stakeholder-mapping)<a href="https://agentmods.dev/skills/doris-labs/sales-skills/stakeholder-mapping"><img src="https://agentmods.dev/badge/skills/doris-labs/sales-skills/stakeholder-mapping/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/doris-labs/sales-skills/stakeholder-mapping"><img src="https://agentmods.dev/badge/skills/doris-labs/sales-skills/stakeholder-mapping.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.00077 | $0.01569 |
| Opus 5.5 | $0.00031 | $0.00628 |
| Sonnet 5.5 | $0.00015 | $0.00314 |
| Haiku 4.5 | $0.00008 | $0.00157 |
Grade A, and why
stakeholder-mapping 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 2mo 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stakeholder Mapping
Purpose
Turn a deal's contact list into a power map: who matters, how much influence each person carries, whether they're for you or against you, and — most importantly — which decision-making roles you have not yet reached. Output a coverage gap list and a concrete plan to access the missing players before they sink the deal.
Inputs
- The list of people you've engaged on the deal (names + titles)
- What each person has said or done (transcripts, emails, your recollection)
- The deal's stage, size, and what you're trying to advance
- Your read on the org chart (reporting lines, who answers to whom)
Method
- List every known contact with title and the last time you interacted.
- Score each person on three axes and place them in the grid below.
- Classify each as champion / blocker / neutral / coach using the rules.
- Run the coverage check: mark which buying roles are filled vs. empty.
- Build the access plan to reach the empty roles.
- Emit the power map in the output format.
Three axes (score each person 1–5):
- Role power — formal authority over the decision and budget.
- Influence — informal sway over the outcome, regardless of title.
- Sentiment — how they feel about you/your solution: −2 (against) to +2 (for).
Power-map grid (role power × influence):
HIGH INFLUENCE LOW INFLUENCE
+----------------------+----------------------+
HIGH POWER | KEY PLAYERS | DORMANT AUTHORITY |
| (must win — econ | (has the title, not |
| buyer, exec sponsor)| engaged — wake them) |
+----------------------+----------------------+
LOW POWER | HIDDEN INFLUENCERS | LOW PRIORITY |
| (no title, big sway —| (keep warm, don't |
| coach, gatekeeper) | over-invest) |
+----------------------+----------------------+
Plot each contact into one quadrant. Annotate each name with sentiment
(+2 … −2). The top-left quadrant is where deals are won or lost.
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.
- 2mo ago First seen · 130 lines · 77 tokens per session scan A 902faccc9fe2
stakeholder-mapping is a skill published in the GitHub repository Doris-Labs/sales-skills (3 stars, last pushed 5mo ago), licensed MIT. It adds 77 tokens to every session and 1,569 once invoked, about $0.0003 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.
stakeholder-mapping compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| stakeholder-mappingDoris-Labs/sales-skills | Skill | 3 | 5mo ago | MIT | A | 77 | Claude Code |
| lynquGravisun/lynqu-ai-toolkit | Skill | 6 | 11d ago | none | A | 40 | Claude Code, Codex |
| lynqu-sales-followupGravisun/lynqu-ai-toolkit | Skill | 6 | 11d ago | none | A | 39 | Claude Code, Codex |
| lynqu-deal-deskGravisun/lynqu-ai-toolkit | Skill | 6 | 11d ago | none | A | 48 | Claude Code, Codex |
| lynqu-event-blitzGravisun/lynqu-ai-toolkit | Skill | 6 | 11d ago | none | A | 47 | Claude Code, Codex |
| lynqu-lead-managementGravisun/lynqu-ai-toolkit | Skill | 6 | 11d ago | none | A | 40 | Claude Code, Codex |
| lynqu-outreachGravisun/lynqu-ai-toolkit | Skill | 6 | 11d ago | none | A | 41 | Claude Code, Codex |