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 LensmorOfficial/trade-show-skills --skill exhibitor-checklist-generatorgit clone --depth 1 https://github.com/LensmorOfficial/trade-show-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/lensmorofficial/trade-show-skills/exhibitor-checklist-generator)<a href="https://agentmods.dev/skills/lensmorofficial/trade-show-skills/exhibitor-checklist-generator"><img src="https://agentmods.dev/badge/skills/lensmorofficial/trade-show-skills/exhibitor-checklist-generator/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/lensmorofficial/trade-show-skills/exhibitor-checklist-generator"><img src="https://agentmods.dev/badge/skills/lensmorofficial/trade-show-skills/exhibitor-checklist-generator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00098 | $0.01579 |
| Opus 5 | $0.00049 | $0.00790 |
| Sonnet 5 | $0.00020 | $0.00316 |
| Haiku 4.5 | $0.00010 | $0.00158 |
Grade A, and why
exhibitor-checklist-generator 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.
How it starts
The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Exhibitor Checklist Generator
Generate a personalized, phased trade show preparation checklist — built from your actual show details, not a generic template with 80% items that don't apply to you.
A good exhibitor checklist is one people actually use. That means: items specific to this show, owners assigned to real functions (not vague "team"), deadlines that are concrete, and a format that works in whatever project management tool the team is using.
When this skill triggers:
- Use it once the team knows enough about the show to start real execution planning
- Use it after budget approval or when a show is likely enough that owners and deadlines matter
- Do not use it for cost modeling; use
trade-show-budget-plannerfor that
Workflow
Step 1: Gather Context
Extract from the user's request. Ask only for what's missing and needed to customize the output.
Required:
- Show name and dates (or approximate timeframe)
- Booth size (sqm or sqft, and type: shell scheme vs. custom build)
- Team size traveling (affects logistics, staffing, and shift planning)
- Primary goal(s): lead generation, product launch, brand awareness, distributor meetings, market entry
Helpful:
- First-time exhibitor or returning? (first-timers need more granular steps)
- Booth location already assigned? (if yes, skip booth selection tasks)
- Shipping origin country (for international shows, customs timelines shift significantly)
- Lead capture system: manual cards, badge scanner rental, CRM-integrated app
- Any special booth elements: AV, demo units, live product demos, hosted meetings
If show dates are not given, generate relative deadlines ("8 weeks before show" instead of a calendar date).
Step 2: Build the Checklist
Output three phases. Adapt the items based on what you know about the user's situation — skip items that obviously don't apply, add items that clearly do.
Phase 1: 8+ Weeks Before Show
Strategic and logistical foundations. Delays here compound into problems later.
What ships with it
2 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.
- 12d ago First seen · 149 lines · 98 tokens per session scan A c464c6b11d90
exhibitor-checklist-generator is a skill published in the GitHub repository LensmorOfficial/trade-show-skills (48 stars, last pushed 1mo ago), licensed MIT. It adds 98 tokens to every session and 1,579 once invoked, about $0.0005 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-30.
Other skills, from other repositories
gsd-tools
Central utility skill for GSD operations. Provides config parsing, slug generation, timestamps, path operations, and orchestrates calls to other specialized skills. Acts as the unified entry point that the original gsd-tools.cjs provided via its lib/ modules (commands, config, core, init).
babysit-babysitter-issues
This skill should be used when the user asks to "babysit issues", "work on assigned issues", "check a5c-agent issues", "process babysitter issues", or wants to find and work on open GitHub issues assigned to a5c-agent in the babysitter repo.
cog-meeting-processing
Process meeting recordings and transcripts into decisions, action items, and team dynamics.
cog-team-intelligence
Cross-reference GitHub, Linear, Slack, and PostHog with bidirectional sync for team briefs.
spec-driven-development
Specification creation and management for the Pilot Shell methodology. Covers semantic search, clarifying questions, structured spec generation, and iterative refinement.
audit-trail
Full traceability from PRD to code commit through the CCPM spec-driven pipeline.