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/alebgl77/claude-inc/call-prepnpx skills add alebgl77/claude-inc --skill call-prepgit clone --depth 1 https://github.com/alebgl77/claude-incWrote 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/alebgl77/claude-inc/call-prep)<a href="https://agentmods.dev/skills/alebgl77/claude-inc/call-prep"><img src="https://agentmods.dev/badge/skills/alebgl77/claude-inc/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 | $0.00075 | $0.00698 |
| Opus 5 | $0.00037 | $0.00349 |
| Sonnet 5 | $0.00015 | $0.00140 |
| Haiku 4.5 | $0.00007 | $0.00070 |
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 5d 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Call Prep — Deal Prepper
"Walk in sharper than anyone on the invite."
When to use
- "Prep me for my call with {company} at {time}"
- "Demo tomorrow — what should I focus on?"
- "Negotiation call, they want a discount"
- Feeds on
account-researchoutput; triggersproposal-builderafter a good call
Workflow
- Situate the deal: stage (first call / discovery / demo / negotiation), what's already been said, what's at stake, who requested the meeting.
- Refresh intel: 5-minute delta on the account — anything new since the brief (news, site changes, replies).
- Attendee angles: per participant — role, what they win if this succeeds, what they fear, one rapport hook.
- Set THE goal: the single outcome that makes this call a win (e.g. "budget owner confirms Q3 window"), plus the fallback outcome.
- Write the question set: 5 discovery questions ordered situation → pain → impact → decision process → timeline; 3 traps to avoid (features monologue, premature pricing, agreeing to unscoped work).
- Demo/negotiation focus (if applicable): the 2 capabilities to show tied to their pains — or the concession ladder: floor price, tradeables (scope, term, case study), walk-away line.
- Compress to one page: the cheat sheet below, glanceable mid-call.
Output format
## Call sheet — {company} · {date/time} · stage: {stage}
GOAL: {one outcome} · Fallback: {outcome}
**Attendees**: {name/role} — wins: ... · fears: ... · hook: ...
**Context delta**: ...
**Open with**: "..."
**Questions (in order)**: 1. ... 5. ...
**Show / Concede**: {demo focus or concession ladder}
**Do NOT**: • ... • ...
**Close with**: "..." → next step proposed on the call
Quality bar
- One explicit goal — not "build rapport"
- Questions follow situation→pain→impact→process→timeline and are open-ended
- Every demo item maps to a stated or hypothesised pain
- Negotiation floor and tradeables written BEFORE the call, not improvised
- Fits on one page; readable at a glance during the call
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.
- 5d ago First seen · 54 lines · 75 tokens per session scan A fc2356019073
call-prep is a skill published in the GitHub repository alebgl77/claude-inc (14 stars, last pushed 2d ago), licensed MIT. It adds 75 tokens to every session and 698 once invoked, about $0.0004 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
mcp-lark
Based on FeiShu(飞书) / Lark's OpenAPI MCP server, manage user information, chats, emails, cloud documents, multidimensional tables, tasks, calendars, etc.
deep-work
Activate when: user says 'I can never find time for focused work', 'I feel busy but produce nothing', 'I keep getting interrupted', 'I want to protect my focus time', 'flow state', 'deliberate practice', 'Cal Newport', or asks how to make progress on hard cognitive work (research, writing, engineering, strategy). Do…
dichotomy-of-control
Activate when: user says "I can't stop worrying about something I can't control," "I'm anxious about how this will turn out," "I keep replaying what went wrong," "I need them to change," "this uncertainty is paralyzing me," or is processing a setback, preparing for a high-stakes unknown outcome, or stuck in…
intrinsic-drive
Activate when: user says 'I've lost motivation', 'I'm burning out', 'the excitement is gone', 'I keep starting things but can't sustain them', 'I'm going through the motions', 'I don't know what drives me anymore', or describes a flat feeling after achieving a major goal. Do NOT activate when: person shows signs of…
knowing-and-doing-as-one
Activate when: user says 'I know I should but I haven't', a team is stuck in analysis paralysis going in circles, you need to assess whether someone actually learned from a past experience, a strategy or lessons-learned doc has produced no operational change, or an organization keeps repeating the same mistake. Do NOT…
lifestage-value-curve
Activate when: someone asks 'what should I focus on at my age,' 'I feel like I'm wasting my best years,' 'how do I plan my career long-term,' 'what does my 40s/50s demand,' or a person is clearly investing for the wrong life stage (Heroic Age execution in the Golden Age, or Silver Age coasting in the Heroic Age). Do…