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-lettergit 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-letter)<a href="https://agentmods.dev/skills/tkcostello/pastor-ai-skills/church-letter"><img src="https://agentmods.dev/badge/skills/tkcostello/pastor-ai-skills/church-letter/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-letter"><img src="https://agentmods.dev/badge/skills/tkcostello/pastor-ai-skills/church-letter.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.00031 | $0.02522 |
| Opus 5 | $0.00015 | $0.01261 |
| Sonnet 5 | $0.00006 | $0.00504 |
| Haiku 4.5 | $0.00003 | $0.00252 |
Grade A, and why
church-letter 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 — 218 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Church Letter Writer
The right words for the hard letters and the good ones.
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
Required:
- The occasion or purpose of the letter
- Key details (what happened, what is changing, what the reader needs to know)
- Audience: whole congregation, a specific group (e.g., volunteers, small group leaders), or an individual
Optional but useful:
- Tone guidance (e.g., "keep it brief," "this is sensitive," "I want this to feel celebratory")
- Anything to avoid: specific phrases, details that should not be in writing, topics that need to stay off the page
- Whether this will be printed, emailed, or both
How This Works
Step 1: Assess the Situation
Before writing a word, I identify the letter type and calibrate tone and length accordingly.
| Letter Type | Tone | Length |
|---|---|---|
| Welcome / celebration | Warm, upbeat | 200-300 words |
| Facility / logistics update | Clear, positive | 150-250 words |
| Leadership transition | Honest, hopeful, pastoral | 300-500 words |
| Staff departure | Careful, gracious, brief | 200-300 words |
| Policy change | Clear, empathetic, firm | 250-400 words |
| Financial update / need | Transparent, vision-driven | 300-400 words |
| Crisis or difficult news | Pastoral, steady, compassionate | 300-500 words |
If the situation does not fit cleanly into one category, I will note that and explain the blend I am using.
Sensitive letters get extra scrutiny before drafting. If the situation contains potential legal exposure (staff termination details, accusations, liability), I will flag it and recommend you involve legal counsel before sending anything in writing.
Step 2: Write the Letter
Every letter follows the same structural logic, adjusted for tone and occasion.
Open with the relationship, not the news.
What ships with it
1 file 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.
- 13d ago First seen · 218 lines · 0 tokens per session scan A 2c0b1ebe0ebc
church-letter is a skill published in the GitHub repository tkcostello/pastor-ai-skills (52 stars, last pushed 16d ago), licensed MIT. It adds 31 tokens to every session and 2,522 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.
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…