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 zackbart/connecta --skill ccbgit clone --depth 1 https://github.com/zackbart/connectaWrote 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/zackbart/connecta/ccb)<a href="https://agentmods.dev/skills/zackbart/connecta/ccb"><img src="https://agentmods.dev/badge/skills/zackbart/connecta/ccb/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/zackbart/connecta/ccb"><img src="https://agentmods.dev/badge/skills/zackbart/connecta/ccb.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.00001 | $0.00523 |
| Opus 5.5 | $0.00000 | $0.00209 |
| Sonnet 5.5 | $0.00000 | $0.00105 |
| Haiku 4.5 | $0.00000 | $0.00052 |
Grade A, and why
ccb 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 6d 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Resolve ids before acting
- Every record is addressed by an integer id. Read it from a list tool and
pass it back; never guess one.
list_individualsfinds people by partial name, phone, or email;familyId,groupId,eventId, form, process, queue, and category ids come from their own list tools. - Events are series with dated occurrences.
list_eventsreturnseventIdplusoccurrence; the attendance tools need both. - Campus and membership-type ids resolve through
ccb_api_geton/campusesand/church/membership_types.
Sensitive data stays out of results
Projections drop allergies, giving numbers and dates, attendance prayer
requests and leader notes, and form payment details; raw: true returns
CCB's full row. Notes, pledges, giving metrics, background checks, and
financial settings are pastoral or financial: read them inside
execute_code and return only the reduced answer the task needs.
Giving in v2 is counts per period (get_giving_metrics), pledges, scheduled
gifts, and financial settings. Transactions, batches, and amounts per gift
live only in CCB's legacy v1 XML API, which this connector does not reach.
Paging
Lists take page (1-based) and perPage (25, 50, 75, or 100 only) and
return page.hasMore, page.nextPage, and page.total. Field names are
CCB's snake_case turned camelCase.
Rate limits
CCB allows each endpoint about one call a second after a burst of 60, per API
client. This connector keeps a per-runtime 60-per-minute window per endpoint
— an approximation, not an enforcement. get_individual (1/s),
list_schedules (1 per 2 s), and individuals advanced search (1 per 5 s)
allow no burst: page a list instead of looping a get, and space those calls.
A rate_limited failure carries CCB's wait.
Raw access
ccb_api_get reaches any GET path; ccb_api_search runs advanced searches,
which CCB serves as POST but are reads.
What ships with it
5 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.
- 6d ago First seen · 56 lines · 1 tokens per session scan A 8460a46ee9fa
ccb is a skill published in the GitHub repository zackbart/connecta (0 stars, last pushed today), licensed MIT. It adds 1 tokens to every session and 523 once invoked, about $0.0000 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-08.
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…