google-form-callback

google-form-callback is a skill for Claude Code, Codex from CALLE-AI/awesome-phone-call-agents. It costs 33 tokens per session (3,110 once invoked), scanned A, original, MIT.

A workflow that turns authorized Google Form responses into reviewed, one-off phone-call candidates and scheduled follow-ups.

In plain words
What is it for?
Use it to inspect eligible form submissions, prepare template-based calls, preview them, schedule runs, and write results back.
Why use it?
It helps process lead, callback, quote-request, appointment, or support forms without calling arbitrary phone numbers or assuming that a form permits contact.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to inspect eligible form submissions, prepare template-based calls, preview them, schedule runs, and write results back.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/calle-ai/awesome-phone-call-agents/google-form-callback
Install

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.

Any agent
npx skills add CALLE-AI/awesome-phone-call-agents --skill google-form-callback
Clone the repo
git clone --depth 1 https://github.com/CALLE-AI/awesome-phone-call-agents

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for google-form-callback

README.md
[![agentmods](https://agentmods.dev/badge/skills/calle-ai/awesome-phone-call-agents/google-form-callback/github.svg)](https://agentmods.dev/skills/calle-ai/awesome-phone-call-agents/google-form-callback)
Your own site
<a href="https://agentmods.dev/skills/calle-ai/awesome-phone-call-agents/google-form-callback"><img src="https://agentmods.dev/badge/skills/calle-ai/awesome-phone-call-agents/google-form-callback/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.

agentmods 80×15 button for google-form-callback

Your own site · 80×15
<a href="https://agentmods.dev/skills/calle-ai/awesome-phone-call-agents/google-form-callback"><img src="https://agentmods.dev/badge/skills/calle-ai/awesome-phone-call-agents/google-form-callback.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,110 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 2 findings, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Excessive Agency · line 274
    Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
    Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
  • medium Rogue Agent · line 14
    Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
    Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00033 $0.03110
Opus 5 $0.00016 $0.01555
Sonnet 5 $0.00007 $0.00622
Haiku 4.5 $0.00003 $0.00311

Measured 12d ago against content hash d145f8e0d1b1, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

google-form-callback 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 12d ago.

The scan reads SKILL.md. This mod also ships 10 executable files (scripts/extract-callback-candidates.mjs, scripts/google-auth.mjs, scripts/google-form-api-client.mjs, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/google-form-callback/SKILL.md · 362 lines

How it starts

The opening of the file, as written. The whole thing — 362 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Google Form Callback

Use this skill when the user wants to process responses from one or more Google Forms and call respondents who submitted a form that clearly authorizes a phone follow-up.

google-form-callback is an intake, scheduling, and safety orchestration skill. It does not create a new phone provider, does not create provider-side recurring schedules, and does not call every phone-looking value in a form. It turns a known form template into reviewed one-off call candidates.

When To Use

Use this skill for:

  • Google Form lead follow-up workflows
  • quote request forms
  • callback request forms
  • appointment or support follow-up forms
  • dry-run previews before placing calls from form submissions
  • scheduled polling of one or more forms

When Not To Use

Do not use this skill to:

  • scrape arbitrary forms for phone numbers
  • call respondents from forms whose description or terms do not authorize phone follow-up
  • infer country codes or repair ambiguous phone numbers
  • create provider-side recurring phone-call jobs
  • expose Google OAuth tokens, provider credentials, confirmation tokens, or full phone numbers in user-facing summaries
  • provide medical, legal, financial, or emergency advice during generated calls

Template Contract

Edit skills/google-form-callback/template.md when the form fields or generated CALL-E goal should change. The extraction script reads this file directly, so field and goal changes should not require code edits.

Do not duplicate business field names or goal text in SKILL.md. Treat template.md as the source of truth for:

  • form fields and required fields
  • the E.164 phone field
  • the recipient name field
  • generated CALL-E goal text
  • writeback result and summary field names

Phone numbers must already be E.164.

Workflow

  1. Confirm the user explicitly wants to process specific Google Forms for callback calls.
  2. Confirm each form's description or terms make phone follow-up clear.
  3. Run auth preflight before any export or dry-run. For an end-to-end callback workflow, Google and CALL-E must both be ready before continuing. If either side is unauthenticated, start the repair flow and stop until the user completes authorization.
  4. Obtain Google Forms metadata and response payloads for the requested form IDs or Drive-discovered forms, plus any submitted-time window, preferably through the local OAuth Google API client.
  5. Extract field slugs from form item descriptions or help text.
  6. Normalize each response into structured fields.
  7. Validate required template fields, E.164 phone numbers, and responseId dedupe state.
  8. Compile the provider goal from skills/google-form-callback/template.md.
  9. Run a dry-run preview first. Show masked phone numbers and skip reasons.
  10. Place calls only after explicit user confirmation or inside an already approved scheduled run.
  11. Record processed responseId values and write the template-defined result and summary fields to the matching row in the linked response spreadsheet.

Read the full file on GitHub · 362 lines

Changes

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.

  1. 12d ago First seen · 362 lines · 33 tokens per session scan A d145f8e0d1b1

Subscribe to this mod's changes

google-form-callback is a skill published in the GitHub repository CALLE-AI/awesome-phone-call-agents (85 stars, last pushed yesterday), licensed MIT. It adds 33 tokens to every session and 3,110 once invoked, about $0.0002 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

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…

vercel/next.js · 103 tokens