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 tahirraufkeeyu/software-development-agent-stack--sdas --skill meeting-prepgit clone --depth 1 https://github.com/tahirraufkeeyu/software-development-agent-stack--sdasWrote 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/tahirraufkeeyu/software-development-agent-stack--sdas/meeting-prep)<a href="https://agentmods.dev/skills/tahirraufkeeyu/software-development-agent-stack--sdas/meeting-prep"><img src="https://agentmods.dev/badge/skills/tahirraufkeeyu/software-development-agent-stack--sdas/meeting-prep/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/tahirraufkeeyu/software-development-agent-stack--sdas/meeting-prep"><img src="https://agentmods.dev/badge/skills/tahirraufkeeyu/software-development-agent-stack--sdas/meeting-prep.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.00062 | $0.02080 |
| Opus 5 | $0.00031 | $0.01040 |
| Sonnet 5 | $0.00012 | $0.00416 |
| Haiku 4.5 | $0.00006 | $0.00208 |
Grade A, and why
meeting-prep 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 10d 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to use
Trigger this skill when:
- A first meeting is booked with a new account and the rep needs prep within 24 hours.
- A second meeting with new attendees (e.g. a technical evaluator added) needs incremental prep.
- A critical stage-gate meeting (exec alignment, procurement kickoff, QBR) is on the calendar.
- A renewal conversation requires context on the customer's last 12 months.
Do not use this for internal meetings or for first-touch cold prospecting — use lead-research for outbound prep.
Inputs
Required:
meeting_context— date/time, meeting purpose, expected length.attendees— list of attendees with name, title, and company. Email addresses help for disambiguation.company_name— the customer or prospect company.
Optional but recommended:
calendar_invite— if parseable, extracts attendees automatically.prior_touches— emails, call notes, Gong summaries from previous conversations.research_brief— iflead-researchhas already been run, pass its output.deal_stage— early / mid / late, affects the agenda shape.our_goal— what we want to leave the meeting with (e.g. "MSA redlines returned," "champion agrees to intro CISO").
Outputs
A one-page Markdown brief:
- Meeting header — who, when, purpose, duration.
- Our success metric — one sentence defining what a successful meeting looks like.
- Company snapshot — 3-5 lines (pulled from or compressed from
research_brief). - Attendees — per person: title, tenure, prior companies, recent LinkedIn activity, inferred priorities.
- Likely priorities by role — for each attendee, 2-3 priorities based on their role and tenure.
- Draft agenda — time-boxed segments with owners.
- Talking points — 3-5 points tied to research, each with a supporting artifact to reference.
- Anticipated objections — 2-4 objections likely to surface, with responses.
- Risks to the meeting — what could derail it, with mitigation.
- Actions / follow-up plan — what we intend to commit to.
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.
- 10d ago First seen · 145 lines · 62 tokens per session scan A 05b77e6d11c0
meeting-prep is a skill published in the GitHub repository tahirraufkeeyu/software-development-agent-stack--sdas (18 stars, last pushed 4mo ago), licensed MIT. It adds 62 tokens to every session and 2,080 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-30.
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…