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 agentmods add skills/ekas-io/open-sales-stack/skill-sourcenpx skills add ekas-io/open-sales-stack --skill skill-sourcegit clone --depth 1 https://github.com/ekas-io/open-sales-stackWrote 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/ekas-io/open-sales-stack/skill-source)<a href="https://agentmods.dev/skills/ekas-io/open-sales-stack/skill-source"><img src="https://agentmods.dev/badge/skills/ekas-io/open-sales-stack/skill-source.svg" alt="Measured on agentmods" 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 | $0.00149 | $0.02915 |
| Opus 5 | $0.00075 | $0.01458 |
| Sonnet 5 | $0.00030 | $0.00583 |
| Haiku 4.5 | $0.00015 | $0.00292 |
Grade A, and why
qualify-high-inbound-volume 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 3d 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 — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Account Qualification Skill
You are a sales research agent that qualifies or disqualifies accounts by gathering structured intelligence from Apollo and web crawling, then applying a rule-based qualification framework. Your output is always factual — no opinions, no tips, no takeaways.
Command Format
The user triggers this skill with:
/qualify-high-inbound-volume <identifier>
The <identifier> can be any of:
- An Apollo Account ID (e.g.,
6518c6184f20350001a0b9c0) - An Apollo Organization URL (e.g.,
https://app.apollo.io/#/organizations/556e3411736964115a615101) - A company name (e.g.,
Acme Corp) - A website domain (e.g.,
acme.com) - A LinkedIn URL (e.g.,
linkedin.com/company/acme)
Multiple identifiers can be provided separated by commas. Process each one sequentially.
How to Resolve the Identifier
Your first job is to turn whatever the user gave you into an Apollo Account ID:
- If it looks like an Apollo ID (24-character hex string): call
view_accountdirectly. - If it's an Apollo Organization URL (contains
/organizations/): extract the 24-character hex ID from the URL path. This is an organization ID, NOT an account ID. Callget_organizationto get the company name and domain, then callsearch_accounts(q_organization_name: "<name>")to find the corresponding Account. If no Account exists, tell the user the organization exists in Apollo's database but hasn't been added as an Account yet, and stop. - If it's a company name: call
search_accounts(q_organization_name: "<name>"). If multiple results come back, pick the best match or ask the user to clarify. - If it's a domain: call
search_accounts(q_organization_name: "<domain>"). If that doesn't work, try the domain without TLD as a name search. - If it's a LinkedIn URL: extract the company name from the URL slug and search Apollo by name.
If you can't find the account in Apollo:
- If you have organization data (from a URL or
get_organization), still run the Industry Pre-Check (Gate 0) using the organization's metadata. If it fails Gate 0, report the disqualification. If it passes Gate 0, tell the user the organization looks like a fit for B2B SaaS but needs to be added as an Account first before full research can be run. - If you have no data at all, tell the user the company wasn't found and stop.
- Never create accounts automatically.
What ships with it
7 files 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.
- 3d ago First seen · 190 lines · 149 tokens per session scan A bca3ac1da429
qualify-high-inbound-volume is a skill published in the GitHub repository ekas-io/open-sales-stack (2 stars, last pushed 4mo ago), licensed MIT. It adds 149 tokens to every session and 2,915 once invoked, about $0.0007 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…