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 recall-outreachgit 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/recall-outreach)<a href="https://agentmods.dev/skills/calle-ai/awesome-phone-call-agents/recall-outreach"><img src="https://agentmods.dev/badge/skills/calle-ai/awesome-phone-call-agents/recall-outreach/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/recall-outreach"><img src="https://agentmods.dev/badge/skills/calle-ai/awesome-phone-call-agents/recall-outreach.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.03377 |
| Opus 5 | $0.00031 | $0.01688 |
| Sonnet 5 | $0.00012 | $0.00675 |
| Haiku 4.5 | $0.00006 | $0.00338 |
Grade A, and why
recall-outreach 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 yesterday.
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 — 283 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Recall Outreach
Use this skill when an organisation has issued a product recall or corrective notice and needs to reach a list of affected customers by phone: read the approved notice, find out whether each person still has the item, offer the return options the business actually runs, and record what each person said in a form someone can audit later.
This is the reusable core of RecallRoute: the
approved-wording contract, the batch call plan, a strict
recipient_result_schema, the idempotency and webhook reconciliation rules, and — most
importantly — the metric model that refuses to report a completed call as a completed recall.
When To Use
- An organisation has approved recall or corrective-notice wording and needs to relay it by phone
- The customers are known, and there is a recorded basis for contacting each of them
- The desired output is a per-customer structured outcome plus a human queue for everything the approved material does not cover
When Not To Use
- Any call where the safe next step is not already decided and written down. This skill relays approved wording; it cannot decide what a customer should do about a hazardous item.
- Emergency notification, injury response, or anything time-critical to physical safety. Never call emergency services.
- Cold outreach, marketing, upselling, or collections dressed as a notice
- Calling anyone the organisation has no recorded authorisation to contact
- Mass-scale dialling. Keep waves small and supervised.
- Any workflow that needs a call cancelled after dispatch — the CALL-E Calls API has no cancel endpoint, so a kill switch can only stop further waves. Say so plainly in your UI.
The Rule This Skill Exists To Enforce
A completed call is not a completed recall.
A recall is finished for a customer when the item is physically back, not when a phone call went
well. Any implementation of this skill must keep those as separate states, and the second must
be reachable only by a named human recording how they know. If you build one boolean called
contacted and set it from a completed call, you have built the thing this skill is designed to
prevent.
What ships with it
9 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.
- assets/sample-campaign.json 3.1 KB
- assets/sample-result-arranged.json 337 B
- assets/sample-result-escalated.json 352 B
- assets/sample-result-invalid.json 340 B
- assets/sample-result-not-reached.json 310 B
- references/examples.md 4.9 KB
- references/result-schema.json 4.3 KB
- references/safety.md 6.9 KB
- scripts/validate-result.mjs 4.4 KB runs code
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.
- yesterday First seen · 283 lines · 62 tokens per session scan A 44fd2b520374
recall-outreach is a skill published in the GitHub repository CALLE-AI/awesome-phone-call-agents (88 stars, last pushed yesterday), licensed MIT. It adds 62 tokens to every session and 3,377 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-09-11.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.