multithreading

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

A sales planning method for involving more people in a deal instead of relying on one contact. It maps roles such as budget owners, users, technical reviewers, blockers, procurement, and legal.

In plain words
What is it for?
Use it to review buying-committee coverage, find introduction paths, and tailor the value of a product to each role.
Why use it?
It reduces the risk that a deal stops when the main contact becomes unavailable and reveals which important roles have not been reached.

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 Use it to review buying-committee coverage, find introduction paths, and tailor the value of a product to each role.

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

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/doris-labs/sales-skills/multithreading"><img src="https://agentmods.dev/badge/skills/doris-labs/sales-skills/multithreading.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 68 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,499 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.00068 $0.01499
Opus 5 $0.00034 $0.00749
Sonnet 5 $0.00014 $0.00300
Haiku 4.5 $0.00007 $0.00150

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

Security

Grade A, and why

multithreading 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/multithreading/SKILL.md · 119 lines

How it starts

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

Multithreading

Purpose

Turn a single-threaded deal into a multi-threaded one: map the full buying committee, see which roles you've actually reached, find warm intro paths from your existing contacts, and equip each persona with the value angle they care about — so the deal survives your champion going quiet.

Inputs

  • The deal and its current contact roster (who you've met, their roles)
  • The deal stage, size, and what you're trying to advance
  • The buying motion (who signs, who blocks, who uses the product)

Method

  1. Coverage analysis against the buying committee. List the roles a deal this size needs, then mark each as engaged, known-not-engaged, or missing:

    • Economic buyer — controls budget, signs the contract.
    • Champion — sells internally for you when you're not in the room.
    • Technical / security evaluator — vets feasibility, integration, compliance.
    • End users — live with the product daily; their adoption is the proof.
    • Blocker / detractor — has reason to say no (incumbent owner, rival initiative).
    • Procurement / legal — gates the paperwork late in the cycle. Score coverage. A deal with only one or two roles engaged is at risk regardless of how good those relationships feel.
  2. Identify intro paths from current contacts. You rarely cold-reach the committee — you get introduced. For each missing role, find the shortest warm path: who among your engaged contacts reports to, works with, or already mentioned that person. Mine call transcripts and email threads for names dropped in passing ("I'll need to check with Priya in security") — those are pre-qualified intro targets.

  3. Per-persona value angle. The same product sells differently to each role. Map one sentence of value per persona before you reach out:

    • Economic buyer — ROI, risk reduction, cost of the status quo, time-to-value.
    • Champion — how this makes them look good and advances their agenda.
    • Technical evaluator — security posture, integration effort, reliability.
    • End users — what daily friction it removes, how little it disrupts them.
    • Procurement — terms, references, predictability, ease of approval. Never recycle the champion pitch for the economic buyer — it lands flat.

Read the full file on GitHub · 119 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 · 119 lines · 68 tokens per session scan A cdba18084922

Subscribe to this mod's changes

multithreading is a skill published in the GitHub repository Doris-Labs/sales-skills (3 stars, last pushed 3mo ago), licensed MIT. It adds 68 tokens to every session and 1,499 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-31.