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 peterod99/consultant-skills --skill multi-threading-enterprise-dealsgit clone --depth 1 https://github.com/peterod99/consultant-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/peterod99/consultant-skills/multi-threading-enterprise-deals)<a href="https://agentmods.dev/skills/peterod99/consultant-skills/multi-threading-enterprise-deals"><img src="https://agentmods.dev/badge/skills/peterod99/consultant-skills/multi-threading-enterprise-deals/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/peterod99/consultant-skills/multi-threading-enterprise-deals"><img src="https://agentmods.dev/badge/skills/peterod99/consultant-skills/multi-threading-enterprise-deals.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.00036 | $0.02187 |
| Opus 5 | $0.00018 | $0.01094 |
| Sonnet 5 | $0.00007 | $0.00437 |
| Haiku 4.5 | $0.00004 | $0.00219 |
Grade A, and why
multi-threading-enterprise-deals 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.
How it starts
The opening of the file, as written. The whole thing — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Multi-Threading Enterprise Deals
When to use
Build relationships with 4–6 stakeholders in a single buyer organization instead of a single champion. Enterprise deals (100k+, 6+ month cycles) have multiple buyers: economic buyer (controls budget), technical buyer (evaluates capability), user champion (day-to-day end-user), potential blockers (finance, legal, operations), and executive sponsor (activates purchasing). Reduce deal risk and maximize scope.
The framework
-
Map the buying committee: Identify the 4–6 stakeholder roles, names, and titles. Use LinkedIn, the prospect's website, and questions during initial calls to build the map.
-
Score by influence + accessibility: Economic buyer (highest priority). Technical buyer (blocks on capability). User champion (easiest entry, lowest influence). Blockers (must know but often reactive). Executive sponsor (comes in late, highest authority).
-
Sequence your outreach: Start with the user champion (relationship and trust). Ladder up to technical buyer (capability validation). Introduce the economic buyer last (decision and budget). Loop in blockers reactively as risk emerges.
-
Tailor value per role: Economic buyer wants ROI and risk reduction. Technical buyer wants capability and integration proof. User champion wants ease-of-use and team adoption. Finance wants cost control and implementation certainty.
-
Surface internal misalignment early: Ask each stakeholder what success looks like. If economic buyer wants speed and technical buyer wants perfect integration, you've found a blocker before it kills the deal. Address it jointly.
-
Protect the deal from single-point-of-failure: If your only contact leaves, the deal dies. Multi-threading ensures at least two stakeholders know why they're considering you.
How to apply it
A $150k enterprise software deal at a mid-market manufacturing company. Your initial contact is the VP of Operations. Day 1 of qualification:
You: "Who else will be involved in evaluating this, like your IT team, your CFO, or your operations team?"
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.
- 11d ago First seen · 136 lines · 36 tokens per session scan A 4985579885f2
multi-threading-enterprise-deals is a skill published in the GitHub repository peterod99/consultant-skills (2 stars, last pushed 4mo ago), licensed MIT. It adds 36 tokens to every session and 2,187 once invoked, about $0.0002 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
strategy-consulting-visualization
Use when turning any content into clear, professional visualizations - board slides, reports, proposals, research summaries, training materials, technical diagrams, infographics, process flows, timelines, benchmarks, waterfall charts, or data-backed visual specs for any audience.
mckinsey-market-research-deck
End-to-end playbook for producing a top-tier, McKinsey-style market-research deck (HTML page-turning presentation + print-ready PDF) for a brand or product category. Covers the research methodology (TAM/SAM/SOM bottom-up, Good/Better/Best framework, competitor profiling, customer pain points, unit economics, business…
mckinsey-deck
Turn any content into a top-tier McKinsey-style deck — a 1280×720 page-turning HTML presentation that also prints to a clean per-slide PDF. Use when the user wants a "McKinsey-style deck / presentation", a polished slide deck or PDF from notes/content, an executive/board/investor deck, or to "make slides / a deck / a…
setup
Interactive setup wizard that configures the GTM Engine for a new user. Collects company context, team info, ICP, personas, messaging, and signals, then generates all config and context files.
good-morning
Daily morning briefing that pulls calendar, tasks, pipeline, and outreach data into one view.
cold-email
Write cold outreach emails using signal-based, pain-first messaging. Improves itself over time.