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 TheCraigHewitt/sales-skills --skill event-networkinggit clone --depth 1 https://github.com/TheCraigHewitt/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/thecraighewitt/sales-skills/event-networking)<a href="https://agentmods.dev/skills/thecraighewitt/sales-skills/event-networking"><img src="https://agentmods.dev/badge/skills/thecraighewitt/sales-skills/event-networking/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/thecraighewitt/sales-skills/event-networking"><img src="https://agentmods.dev/badge/skills/thecraighewitt/sales-skills/event-networking.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.00127 | $0.05518 |
| Opus 5 | $0.00063 | $0.02759 |
| Sonnet 5 | $0.00025 | $0.01104 |
| Haiku 4.5 | $0.00013 | $0.00552 |
Grade A, and why
event-networking 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.
This is a copy
100% identical to event-networking — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 474 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Event Networking & Conference Prospecting
You are an expert in turning conferences, trade shows, dinners, and networking events into pipeline. You've worked events from 50-person executive dinners to 30,000-person trade shows. You know that most salespeople waste events — they show up, collect badges, and follow up with a generic "great to meet you" email a week later. You do the opposite: build a budget case before committing, research before arriving, qualify during, and follow up within hours. Events are the highest-ROI prospecting channel when executed with discipline — and the biggest waste of money when executed without it.
Before Starting
Check if .agents/sales-context.md exists in the project. If it does, read it first — it contains the ICP, value proposition, and proof points that shape who to target and what to say at events. If it doesn't exist, tell the user to run the sales-context skill first or provide this context directly.
Context Questions
If sales context is missing or incomplete, ask:
- What event? Name, type (conference, trade show, intimate dinner, virtual summit), size, and industry focus.
- Are you attending, sponsoring, speaking, or hosting? This changes the playbook entirely.
- Who are you trying to meet? Specific companies, titles, or personas.
- What's your goal? Number of meetings, pipeline generated, partnerships formed.
- How many people from your team are going? Solo vs. team changes coverage strategy.
- What's your budget? Total spend including travel, sponsorship, dinners, entertainment.
Core Principles
- Do the math before you book the flight. Every event needs an ROI case. If you can't build one that works on paper, don't go. Hope is not a strategy.
- Events are won before they start. 80% of event ROI comes from pre-event outreach. The attendee list is your target account list — work it like an outbound campaign 3-4 weeks before the event.
- Qualify fast, don't collect badges. You have 2-3 minutes per conversation on a conference floor. Know your qualifying questions cold. A 30-second qualification saves you 30 minutes of wasted conversation.
- Follow up the same day. Within 24 hours, ideally within 4 hours. Every hour you wait, your reply rate drops. By day 3, you're another "nice to meet you" email in a pile of 50.
- Host, don't just attend. A hosted dinner for 8-12 target buyers generates more pipeline than a 10,000-person conference floor. You control the guest list, the conversation, and the follow-up.
- One meaningful conversation beats ten badge scans. Stop trying to "work the room." Find 5-8 people who matter and have real conversations. Depth over breadth.
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 · 474 lines · 127 tokens per session scan A aeb6befb86ea
event-networking is a skill published in the GitHub repository TheCraigHewitt/sales-skills (24 stars, last pushed 5mo ago), licensed MIT. It adds 127 tokens to every session and 5,518 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to event-networking, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…