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 psenger/catholic-ai-skills --skill releasegit clone --depth 1 https://github.com/psenger/catholic-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/psenger/catholic-ai-skills/release)<a href="https://agentmods.dev/skills/psenger/catholic-ai-skills/release"><img src="https://agentmods.dev/badge/skills/psenger/catholic-ai-skills/release/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/psenger/catholic-ai-skills/release"><img src="https://agentmods.dev/badge/skills/psenger/catholic-ai-skills/release.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.00139 | $0.01910 |
| Opus 5 | $0.00069 | $0.00955 |
| Sonnet 5 | $0.00028 | $0.00382 |
| Haiku 4.5 | $0.00014 | $0.00191 |
Grade A, and why
release 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 10d 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.
This is a copy
100% identical to release — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 227 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release
Ships completed work. The skill detects context and runs the right phase:
- On a feature branch with committed work → WRAP UP phase
- On main after a merge → CUT RELEASE phase
For all message formatting, follow the conventions skill.
Step 0 — Auth & Identity (always)
Check for a GitHub MCP server in available tools. If none:
gh auth status
Stop if neither is available: "I need the GitHub MCP server or gh CLI authenticated. Run gh auth login."
Confirm identity — use mcp__github__get_me if the GitHub MCP server is available, otherwise:
gh api user --jq '"@\(.login) — \(.name)"'
Show the result and ask: "I'll be acting as @username — is that right?" Wait for confirmation.
WRAP UP Phase
Triggered when on any non-main branch (feature/, fix/, chore/, refactor/, test/, etc.) with a clean working tree.
Step 1 — Verify State
git branch --show-current # must not be main
git status --porcelain # must be empty — all work committed
If the tree is dirty, stop: "You have uncommitted changes. Commit or stash them first."
Step 2 — Detect What Changed
git diff main...HEAD --name-only
Determine:
- Was a new skill added? Look for a new directory under
skills/not present on main. - Was an existing skill modified? Look for changes inside
skills/<name>/. - Is this a bug fix, refactor, or docs change? Look at changed files outside
skills/.
Derive the issue number from the branch name (e.g. feature/14-add-handoff-skill → #14).
If none found, ask the user for the issue number.
Step 3 — Update Admin Files
CHANGELOG.md — add a bullet to ## [Unreleased] under the correct subsection:
- New skill →
### Added - Updated skill →
### Changed - Bug fix →
### Fixed
Bullet format (see conventions skill):
- **skill-name** — <what changed and why>. ([#N](issue-url))
README.md — only if a new skill was added:
- Add a row to the skills table
- Add a
### skill-nameprose section following the existing pattern
What ships with it
4 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.
- 10d ago First seen · 227 lines · 139 tokens per session scan A 40707a1269a3
release is a skill published in the GitHub repository psenger/catholic-ai-skills (2 stars, last pushed 3mo ago), licensed MIT. It adds 139 tokens to every session and 1,910 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to release, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
updater_guide
Guidance for checking for and installing Row-Bot updates.
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.