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 akiotanaka847/qaio-desktop --skill prep-a-meetinggit clone --depth 1 https://github.com/akiotanaka847/qaio-desktopWrote 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/akiotanaka847/qaio-desktop/prep-a-meeting)<a href="https://agentmods.dev/skills/akiotanaka847/qaio-desktop/prep-a-meeting"><img src="https://agentmods.dev/badge/skills/akiotanaka847/qaio-desktop/prep-a-meeting/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/akiotanaka847/qaio-desktop/prep-a-meeting"><img src="https://agentmods.dev/badge/skills/akiotanaka847/qaio-desktop/prep-a-meeting.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.00068 | $0.01636 |
| Opus 5 | $0.00034 | $0.00818 |
| Sonnet 5 | $0.00014 | $0.00327 |
| Haiku 4.5 | $0.00007 | $0.00164 |
Grade A, and why
prep-a-meeting 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 7d 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prep A Meeting
One skill, two meeting-prep shapes. type param pick structure. Playbook-grounding + "no generic templates" shared.
Parameter: type
call- pre-call one-pager (discovery / demo / followup / late-stage). Goal · attendees · questions · objections · exit criteria.account-review- quarterly account review pack for existing customer. Outcomes · usage trend · open asks · risks · next-quarter goal.
User ask names type plain English ("call prep", "account review") → infer. Else ask ONE question naming 2 options.
When to use
- Explicit triggers in description.
- Implicit:
brief-me-for-todaydetect imminent meeting no prep, chain here fortype=call; customer-retention routine chain here fortype=account-reviewbefore renewal window.
Connections I need
I run external work through Composio. Before this skill runs I check that the categories below are linked. Missing → I name the category, ask you to connect it from the Integrations tab, stop.
- Calendar - pull meeting time and attendees. Required.
- CRM - read the deal or customer record (stage, owner, contacts). Required.
- Meetings - pull prior call transcripts for
type=call. Optional. - Social - enrich attendee profiles via LinkedIn. Optional.
- Billing - pull billing state for
type=account-review. Optional.
If calendar or CRM aren't connected I stop and ask you to connect them first - prep is grounded in the meeting and the deal.
Information I need
I read your sales context first. For every required field that's missing I ask ONE plain-language question (best modality: connected app > file drop > URL > paste) and wait.
- Your sales playbook - Required. Why I need it: I prioritize questions against your qualification framework and pull your primary first-call goal. If missing I ask: "I don't have your playbook yet - want me to draft it now?"
- Which meeting this is for - Required. Why I need it: I pull the calendar event, attendees, and the deal it ties to. If missing I ask: "Which meeting do you want me to prep - who's it with and roughly when?"
- Connected CRM - Required. Why I need it: I read deal stage and prior touches to focus the question bank. If missing I ask: "Connect your CRM (HubSpot, Salesforce, Attio, Pipedrive, or Close), or paste the deal context."
- Product usage source - Optional, helpful for
type=account-review. Why I need it: I cite real usage trends. If you don't have it I keep going with TBD on the usage section.
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.
- 7d ago First seen · 94 lines · 68 tokens per session scan A 0b5b167f537c
prep-a-meeting is a skill published in the GitHub repository akiotanaka847/qaio-desktop (2 stars, last pushed 8d ago), licensed MIT. It adds 68 tokens to every session and 1,636 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-09-05.
Other skills, from other repositories
afrexai-lead-hunter
Enterprise-grade B2B lead generation, enrichment, scoring, and outreach sequencing for AI agents. Find ideal prospects, enrich with verified data, score against your ICP, and generate personalized outreach — all autonomously.
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…
proposals
Use when writing the document a buyer reads to say yes — a commercial proposal or Statement of Work, turning discovery notes into a scoped and priced document, adding tiers so the middle one wins, or diagnosing a proposal that will not close. NOT the binding legal agreement with its liability and IP clauses (that is…
handle-demo-request
Use this skill when someone requests a demo through your website — a "Book a demo" form, a webhook carrying little more than a work email — and the question is what happens in the next sixty seconds. Enriches the person and company, decides fit and buyer persona separately, and routes the request down one of three…
rfp-response
Use this skill when an inbound RFP, RFI, or brief lands and a proposal has to go back by a deadline - "an RFP just came in", "should we bid on this", "build the response", "the proposal is due Friday", "set up the RFP", "where are we on the [brand] RFP", "what's the status of our RFPs", "which RFP is about to slip".…
co-founder-dynamics
Complete co-founder playbook for technical founders — finding co-founders, equity splits (dynamic and static), co-founder agreements, vesting schedules, working relationships, conflict resolution, co-founder breakups, and the "dating before marrying" framework. Use when looking for a co-founder, structuring a founding…