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 tkcostello/pastor-ai-skills --skill church-emailgit clone --depth 1 https://github.com/tkcostello/pastor-ai-skillsWrote 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/tkcostello/pastor-ai-skills/church-email)<a href="https://agentmods.dev/skills/tkcostello/pastor-ai-skills/church-email"><img src="https://agentmods.dev/badge/skills/tkcostello/pastor-ai-skills/church-email/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/tkcostello/pastor-ai-skills/church-email"><img src="https://agentmods.dev/badge/skills/tkcostello/pastor-ai-skills/church-email.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00024 | $0.01923 |
| Opus 5 | $0.00012 | $0.00962 |
| Sonnet 5 | $0.00005 | $0.00385 |
| Haiku 4.5 | $0.00002 | $0.00192 |
Grade A, and why
church-email 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 13d 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 — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Weekly Church Email Writer
Turn your announcements into an email people actually open.
Before writing: follow the pastor-foundation skill and load the church profile from
~/.claude/pastor-profile.md. If the profile file is missing, run the pastor-setup skill first.
What to Give Me
Paste in whatever you have. It does not need to be clean. Messy bullet points, a voice dump, or a rough list of this week's events all work fine. I will organize it.
Required:
- This week's announcements, events, or sermon recap (any format)
Optional but useful:
- A personal note or pastoral thought you want to include
- Any prayer request you want to emphasize
- Seasonal or series theme (e.g., "we're in week 3 of our Anxiety series")
- Service times or location if not set in pastor-foundation
How This Works
Step 1: Organize the Content
Before writing a word, I sort what you gave me into a logical structure:
- Lead item: The single most important thing your congregation needs to know or do this week. This goes first. No exceptions.
- Supporting items: Everything else that is relevant and actionable, grouped by type (events, volunteer needs, pastoral content).
- Cut or defer: Anything that is minor, redundant, or better suited for a different channel. If you sent me 8 items, I will flag what I cut and why.
The goal is a clear priority order before any drafting begins. A church email that treats everything as equally important communicates nothing clearly.
Step 2: Write the Email
Every weekly email has six components. Here is exactly how each one works:
Subject Line
- Under 50 characters
- Specific, not generic. "This Week at Grace Community" is a skip. "Kids Camp spots are almost gone" gets opened.
- Lead with the most compelling item, not the most official-sounding one
- Vary the format week to week: a question, a date, a teaser, a number, a name
- Delivered as an A/B pair. Use A as the default; B as an alternative angle
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.
- 13d ago First seen · 217 lines · 24 tokens per session scan A 21901bc49780
church-email is a skill published in the GitHub repository tkcostello/pastor-ai-skills (52 stars, last pushed 15d ago), licensed MIT. It adds 24 tokens to every session and 1,923 once invoked, about $0.0001 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…