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 is-it-accessiblegit 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/is-it-accessible)<a href="https://agentmods.dev/skills/calle-ai/awesome-phone-call-agents/is-it-accessible"><img src="https://agentmods.dev/badge/skills/calle-ai/awesome-phone-call-agents/is-it-accessible/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/is-it-accessible"><img src="https://agentmods.dev/badge/skills/calle-ai/awesome-phone-call-agents/is-it-accessible.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.00099 | $0.04057 |
| Opus 5.5 | $0.00040 | $0.01623 |
| Sonnet 5.5 | $0.00020 | $0.00811 |
| Haiku 4.5 | $0.00010 | $0.00406 |
Grade A, and why
is-it-accessible 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 — 371 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Is it accessible?
Whether a place actually works for a disabled person is almost never on its website. Where accessibility data exists at all it is one flattened claim — "wheelchair accessible: yes" — that hides the detail deciding the trip: how many steps at the door, whether the accessible toilet is up a flight of stairs, whether the lift is working today, whether staff will write things down.
So people ring round venues before every outing. That phone work is unpaid, repetitive, and falls on the person with the least energy to spare. This skill does the ringing and brings back an answer you can act on.
What it is not: an inspection, an audit, or a legal determination. It records what staff said on the phone. Staff answer in good faith about buildings they did not design, and they are sometimes wrong. Treat the result as a much better starting point than a website, not as a guarantee.
When to use this skill
- Someone is planning a visit and needs to know whether a specific venue works for their specific needs.
- Someone has a shortlist of three or four venues and wants them ranked.
- A published accessibility claim needs checking against what staff say.
When not to use it
- To audit a venue for compliance, or to build a case against one. This asks questions; it does not assess anyone against a standard.
- To call a venue repeatedly. One call per venue per enquiry. A business rung three times by the same tool is a nuisance, and the answers will not improve.
- To call domestic or personal numbers. This is for businesses and public venues.
- Without the person's explicit go-ahead for this specific call.
Before you start
You need three things.
A profile. The needs that matter to this person, each marked must-have or
nice-to-have. Copy assets/example-profile.json and edit it. Run
node scripts/check_access.mjs --list-needs to see all 30 need ids and the
question each one asks. Maximum 12 needs per profile — a call that runs past a
dozen questions outlasts the patience of whoever picked up, and the later
answers get terse and unreliable.
What ships with it
8 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 · 371 lines · 99 tokens per session scan A 8ad3a9a3ce00
is-it-accessible is a skill published in the GitHub repository CALLE-AI/awesome-phone-call-agents (109 stars, last pushed yesterday), licensed MIT. It adds 99 tokens to every session and 4,057 once invoked, about $0.0004 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
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…
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…