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 midweek-devotionalgit 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/midweek-devotional)<a href="https://agentmods.dev/skills/tkcostello/pastor-ai-skills/midweek-devotional"><img src="https://agentmods.dev/badge/skills/tkcostello/pastor-ai-skills/midweek-devotional/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/midweek-devotional"><img src="https://agentmods.dev/badge/skills/tkcostello/pastor-ai-skills/midweek-devotional.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.00032 | $0.01491 |
| Opus 5 | $0.00016 | $0.00745 |
| Sonnet 5 | $0.00006 | $0.00298 |
| Haiku 4.5 | $0.00003 | $0.00149 |
Grade A, and why
midweek-devotional 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 12d 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Midweek Devotional
A pastoral moment for the middle of the week.
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 You Need to Provide
Required:
- A verse, passage, or theme
Optional:
- Connection to your current sermon series
- Something happening in the community or world that's on people's minds
Step 1: Write the Devotional
Use this exact structure. Every section has a purpose. Don't skip any of them.
Opening (1-2 sentences)
Meet the reader where they are on Wednesday. Not where you wish they were.
The opening should be honest and human. Skip the greeting entirely. Drop the reader into a real moment.
What not to write: "Happy Wednesday, church family!"
What to aim for: "By Wednesday most of us have already forgotten what we committed to on Sunday. That's not failure. That's being human."
The goal is immediate recognition. The reader should think: "That's exactly where I am right now."
Scripture (quoted in full)
Pull 1-3 verses. Not a full chapter. The whole passage should fit in a single short paragraph.
Use the pastor's preferred translation. If no preference is given, use the ESV or NIV, whichever reads more naturally for the text.
Quote it cleanly. No verse-by-verse breakdown. Let the text breathe.
Reflection (3-5 sentences)
This is the heart of the devotional.
Write in first person. Write as a pastor who has been sitting with this text for days, not someone summarizing a commentary. What does this passage mean for THIS week, in THIS moment, for people carrying real weight?
Be specific. Vague spiritual encouragement does nothing. Anchor the reflection to something concrete: a feeling, a situation, a tension people are actually navigating.
Keep sentences short. Two to three per paragraph. Midweek readers are scanning while eating lunch or driving carpool. Make every sentence earn its place.
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.
- 12d ago First seen · 154 lines · 32 tokens per session scan A b249c2b5d229
midweek-devotional is a skill published in the GitHub repository tkcostello/pastor-ai-skills (52 stars, last pushed 15d ago), licensed MIT. It adds 32 tokens to every session and 1,491 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…