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 Arise-AI-Group/lead-management-plugin --skill discovery-prepgit clone --depth 1 https://github.com/Arise-AI-Group/lead-management-pluginWrote 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/arise-ai-group/lead-management-plugin/discovery-prep)<a href="https://agentmods.dev/skills/arise-ai-group/lead-management-plugin/discovery-prep"><img src="https://agentmods.dev/badge/skills/arise-ai-group/lead-management-plugin/discovery-prep.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.1 | $0.00000 | $0.02029 |
| Opus 5 | $0.00000 | $0.01014 |
| Sonnet 5 | $0.00000 | $0.00406 |
| Haiku 4.5 | $0.00000 | $0.00203 |
Grade A, and why
discovery-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 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 — 294 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Discovery Prep
Get fully prepared for any discovery or sales call. Build a meeting brief with company research, attendee backgrounds, a prep questionnaire, and a suggested agenda — plus automate the pre-meeting email sequence.
How It Works
┌─────────────────────────────────────────────────────────────────┐
│ DISCOVERY PREP │
├─────────────────────────────────────────────────────────────────┤
│ STANDALONE (always works) │
│ ✓ You tell me: company, meeting type, attendees │
│ ✓ Web research: company info, news, leadership │
│ ✓ Pre-meeting email sequence drafts (3 emails) │
│ ✓ Prep questionnaire (7 key questions) │
│ ✓ Meeting brief with agenda and discovery questions │
├─────────────────────────────────────────────────────────────────┤
│ SUPERCHARGED (when you connect your tools) │
│ + Calendar: Auto-detect bookings, pull attendees and time │
│ + CRM: Pull lead history, prior interactions, pipeline data │
│ + Email: Send confirmation, questionnaire, reminder sequence │
│ + Transcripts: Pull prior call recordings for returning leads │
└─────────────────────────────────────────────────────────────────┘
Getting Started
Required:
- Company or contact name
- Meeting date/time (or "tomorrow at 2pm")
Helpful if you have it:
- Attendee names and titles
- What you know about them so far (form submission, referral context, prior conversations)
- What you want to accomplish in the meeting
If calendar is connected, I'll find the meeting automatically and pull attendees.
Connectors (Optional)
| Connector | What It Adds |
|---|---|
| ~~calendar | Auto-detect booking, pull meeting details, attendees, description |
| ~~CRM | Lead history, prior interactions, qualification score, form submission data |
| Send the 3-email pre-meeting sequence automatically | |
| ~~conversation intelligence | Pull prior call recordings if this is a returning lead |
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 · 294 lines · 0 tokens per session scan A 7e3c2474a87d
discovery-prep is a skill published in the GitHub repository Arise-AI-Group/lead-management-plugin (7 stars, last pushed 7mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,029 tokens. 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.
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…
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…