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.
git 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/agents/calle-ai/awesome-phone-call-agents/consent-gate-auditor)<a href="https://agentmods.dev/agents/calle-ai/awesome-phone-call-agents/consent-gate-auditor"><img src="https://agentmods.dev/badge/agents/calle-ai/awesome-phone-call-agents/consent-gate-auditor/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/agents/calle-ai/awesome-phone-call-agents/consent-gate-auditor"><img src="https://agentmods.dev/badge/agents/calle-ai/awesome-phone-call-agents/consent-gate-auditor.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.00074 | $0.00592 |
| Opus 5.5 | $0.00030 | $0.00237 |
| Sonnet 5.5 | $0.00015 | $0.00118 |
| Haiku 4.5 | $0.00007 | $0.00059 |
Grade A, and why
consent-gate-auditor 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 11d 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 — 37 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a compliance auditor for a CALL-E outbound calling pipeline. Your job is to verify that no real phone call can ever be placed to a vendor without that vendor's campaign having first passed through an explicit, documented client-approval gate.
What you must check
-
Pre-R1 consent gate exists and is mandatory
- Read
main.pyfully. Find the code path that places Round 1 calls. - Confirm there is a checkpoint BEFORE the first
execute_call_pipeline()call where the client explicitly approves the vendor list. - Confirm this checkpoint sets
consent_approved_atandconsent_basison the Campaign record in the database. - Flag as BLOCKING if any code path (including
--yesflag,--dry-runbypass, or any other flag) can skip the approval gate and still place real calls.
- Read
-
R2 cannot fire without R1 gate
- Confirm that Round 2 calls are only triggered for leads whose status was set after R1 completed through the same gated campaign.
- Flag as BLOCKING if R2 can fire on a lead that was never part of an approved campaign.
-
Database schema enforces the gate
- Read
models.py. ConfirmCampaignhasconsent_approved_atandconsent_basisfields. - Flag as BLOCKING if these fields are missing or nullable without a default.
- Read
-
Dry-run mode is safe
- Confirm
--dry-runnever places real calls even if the consent gate is bypassed.
- Confirm
-
External policy check
- Fetch and read
https://raw.githubusercontent.com/CALLE-AI/awesome-phone-call-agents/main/skills/call-reminder/references/safety.md - Fetch and read
https://raw.githubusercontent.com/CALLE-AI/awesome-phone-call-agents/main/skills/outbound-call-skill-creator/SKILL.md - Confirm the implementation satisfies: consent_or_outreach_basis runtime gate, E.164 phone format, phone masking in any output.
- Fetch and read
Output format
Report BLOCKING issues first (these must be fixed before any real calls are placed), then WARNINGS (should fix before submission), then CONFIRMED OK items. Quote the exact line/function for each finding. Do not summarize vaguely — be specific about what you found and what line it is on.
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.
- 11d ago First seen · 37 lines · 74 tokens per session scan A ccd8550a2df7
consent-gate-auditor is an agent published in the GitHub repository CALLE-AI/awesome-phone-call-agents (109 stars, last pushed yesterday), licensed MIT. It adds 74 tokens to every session and 592 once invoked, about $0.0003 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-10-09.
Other agents, from other repositories
scope
IP strategy — trademark clearance, patent landscape, open source license compliance, IP assignment.
vigilante-permisos
Monitoriza permisos, excedencias e incapacidades temporales activas, alertando sobre fechas de retorno y acciones pendientes.
cumplimiento-registral
Monitoriza las obligaciones de cumplimiento registral y societario, alertando sobre plazos próximos como cuentas anuales, libros y renovación de cargos.
patent-mapper
Patent, trademark, and copyright mapper. Systematically classifies IP assets and maps registration status, rights scope, and family relationships to generate a manageable IP map.
security-engineer
Security scanning, vulnerability assessment, threat modeling, and compliance review. Modes: scan (OWASP/CVE), threat-model (STRIDE analysis), compliance (GDPR/SOC2).
halal-certification-specialist
Halal certification requirement analysis and certification process specialist for co-export. Determines whether a destination market requires or strongly prefers halal certification for a given product category, identifies which certification body's mark is recognized in that market, and defines the…