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 CALLE-AI/awesome-phone-call-agents --skill email-task-call-proposalgit clone --depth 1 https://github.com/CALLE-AI/awesome-phone-call-agentsWrote 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/calle-ai/awesome-phone-call-agents/email-task-call-proposal)<a href="https://agentmods.dev/skills/calle-ai/awesome-phone-call-agents/email-task-call-proposal"><img src="https://agentmods.dev/badge/skills/calle-ai/awesome-phone-call-agents/email-task-call-proposal/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/calle-ai/awesome-phone-call-agents/email-task-call-proposal"><img src="https://agentmods.dev/badge/skills/calle-ai/awesome-phone-call-agents/email-task-call-proposal.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.00039 | $0.00991 |
| Opus 5.5 | $0.00016 | $0.00396 |
| Sonnet 5.5 | $0.00008 | $0.00198 |
| Haiku 4.5 | $0.00004 | $0.00099 |
Grade A, and why
email-task-call-proposal 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 1mo 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Email Task Call Proposal
This skill helps an assistant notice work in email, task, and calendar systems that needs an external follow-up. It chooses the least surprising channel available — an existing booking system, email, or phone — and creates a structured proposal for a human to review. It does not place a call while reading sources or drafting the proposal.
The intended host workflow is:
email/task/calendar evidence → channel proposal → human approval → follow-up → structured result
Use this skill when
- an email, task, or calendar event explicitly asks for a callback, confirmation, reschedule, availability check, or another bounded follow-up;
- a calendar event needs to be reorganized and the original booking channel is known or can be inferred from direct source evidence; and
- the recipient and an exact contact method are present in the source or a directly matched contact record.
Do not use this skill when
- the phone number or email address is missing, ambiguous, guessed, or found only in an unrelated contact record;
- the task can be completed safely by email, a draft, a calendar action, or a normal task update;
- the source does not establish why this recipient should be called;
- the user has not approved the proposal; or
- the call would require making a legal, medical, financial, purchasing, or other consequential decision on the user's behalf.
Channel selection
When a user asks to reorganize or reschedule an event, inspect how it was originally arranged before choosing a channel:
- Check durable channel memory for the exact person/business and situation first. A specific memory such as "reschedule appointment → phone" overrides a general preference, but never apply a memory to a merely similar business.
- Use the original booking system when the event contains a supported booking link or provider identifier.
- Use email when the source thread or directly matched contact has an email address and the business normally handles changes there.
- Use CALL-E when the business has no usable email or booking workflow, the source/contact has an explicit phone number, and the requested change can be stated as one bounded call goal. A phone-only salon or barber is a canonical example.
- If more than one channel is plausible, present the choice in the proposal instead of silently trying several channels. Never create duplicate email and phone follow-ups for the same event without separate approval.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 97 lines · 39 tokens per session scan A 70b04d55de9c
email-task-call-proposal is a skill published in the GitHub repository CALLE-AI/awesome-phone-call-agents (109 stars, last pushed yesterday), licensed MIT. It adds 39 tokens to every session and 991 once invoked, about $0.0002 per session on Opus 5.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-15.
Other skills, from other repositories
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
agentmail
Use your assigned AgentMail inbox to read email tasks, explicitly send or reply, and check delivery. Provided automatically by your inbox assignment.
rowboat-spaces
How to work as a member of Rowboat Spaces, the team chat where people and agents work together. Load it once per session, before acting on any request that reaches you from Rowboat; it covers your setup, mentions and hand-offs, the tools, and files.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…