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 agentmods add skills/everyone-needs-a-copilot/claude-copilot/call-prepnpx skills add Everyone-Needs-A-Copilot/claude-copilot --skill call-prepgit clone --depth 1 https://github.com/Everyone-Needs-A-Copilot/claude-copilotWrote 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/everyone-needs-a-copilot/claude-copilot/call-prep)<a href="https://agentmods.dev/skills/everyone-needs-a-copilot/claude-copilot/call-prep"><img src="https://agentmods.dev/badge/skills/everyone-needs-a-copilot/claude-copilot/call-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.00082 | $0.01791 |
| Opus 5 | $0.00041 | $0.00896 |
| Sonnet 5 | $0.00016 | $0.00358 |
| Haiku 4.5 | $0.00008 | $0.00179 |
Grade A, and why
call-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 today.
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 call-prep — 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 — 259 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Call Prep
Get fully prepared for any sales call in minutes. This skill works with whatever context you provide, and gets significantly better when you connect your sales tools.
How It Works
┌─────────────────────────────────────────────────────────────────┐
│ CALL PREP │
├─────────────────────────────────────────────────────────────────┤
│ ALWAYS (works standalone) │
│ ✓ You tell me: company, meeting type, attendees │
│ ✓ Web search: recent news, funding, leadership changes │
│ ✓ Company research: what they do, size, industry │
│ ✓ Output: prep brief with agenda and questions │
├─────────────────────────────────────────────────────────────────┤
│ SUPERCHARGED (when you connect your tools) │
│ + CRM: account history, contacts, opportunities, activities │
│ + Email: recent threads, open questions, commitments │
│ + Chat: internal discussions, colleague insights │
│ + Transcripts: prior call recordings, key moments │
│ + Calendar: auto-find meeting, pull attendees │
└─────────────────────────────────────────────────────────────────┘
Getting Started
When you run this skill, I'll ask for what I need:
Required:
- Company or contact name
- Meeting type (discovery, demo, negotiation, check-in, etc.)
Helpful if you have it:
- Who's attending (names and titles)
- Any context you want me to know (paste prior notes, emails, etc.)
If you've connected your CRM, email, or other tools, I'll pull context automatically and skip the questions.
Connectors (Optional)
Connect your tools to supercharge this skill:
| Connector | What It Adds |
|---|---|
| CRM | Account details, contact history, open deals, recent activities |
| Recent threads with the company, open questions, attachments shared | |
| Chat | Internal chat discussions (e.g. Slack) about the account, colleague insights |
| Transcripts | Prior call recordings, topics covered, competitor mentions |
| Calendar | Auto-find the meeting, pull attendees and description |
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.
- today First seen · 259 lines · 82 tokens per session scan A 51b075cf1a1c
call-prep is a skill published in the GitHub repository Everyone-Needs-A-Copilot/claude-copilot (13 stars, last pushed today), licensed MIT. It adds 82 tokens to every session and 1,791 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to call-prep, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
cadence-first
Meta-orchestrator: assigns skill-chain cadence per block (Tier 1/2/3) via Q1-Q6 rules. Reads target taskblocks + task.md, writes cadence-decisions-{R}.md artifact. Standalone (executor invokes) or Batch (generator hand-off). Use when: deciding cadence for a batch of blocks, generator hand-off from decomposition skills.
ship-first
Final task completion protocol: report → user-note → deploy → smoke test → close? → guide? → routing.db → propagate → STATUS → sessions. Invoked from fast-track and pipeline flows after task execution, not directly by the user. Use when: invoked after the execute step of a fast-track or pipeline task.
ui-ai-first
Final audit of a large task before closure — finds which operations are available only via code / curl / SQL and decides per each: automate with a skill or AI agent (A) or create a UI task (B). Protects against invisible usability debt. Walks through each implemented block: reads task.md + reports + guides + code →…
decision-first
Makes an architectural / project / scope decision using a 5-part model INSTEAD of asking the user. Structure: 🎯 Decision / Why / 🛡 Security / 📈 Scalability / Alternatives / Plain-language analogy. 1 question = 1 atomic artifact. Use when: the agent is about to ask an architectural / scope question…
library-first
Mandatory protocol before executing any fast-track task. Analyzes the task, builds a table: what we do / where it comes from / how many lines of code. Principle: maximum reuse of existing libraries and components, minimum new code. Waits for explicit user approval — does nothing until confirmed. Use when: fast-track…
fixture-new
Creates a parity fixture — the frozen scenario plus the contract its output must satisfy. Asks which skill and case, what shape the run must produce, and writes input.md and expect.yml. Ends by proving the new fixture actually fails on an empty directory. A fixture that passes when nothing ran is worse than no…